Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335799 - [Forms] Cocoa Forms do not get updated on platform preference change.
Summary: [Forms] Cocoa Forms do not get updated on platform preference change.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.7   Edit
Hardware: Macintosh Mac OS X
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 19:54 EST by Miles Parker CLA
Modified: 2019-09-24 13:57 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2011-01-30 19:54:05 EST 
OK, now we're getting pretty trivial, but it bugs me. :) When user changes platform color selection (currently highlight, but see earlier bug) the forms do not change color until the application is restarted. Note that other UI elements do update immediately.
Comment 1 Prakash Rangaraj CLA 2011-01-31 01:53:29 EST 
Forms API is owned by UA
Comment 2 Chris Goldthorpe CLA 2011-02-01 18:01:26 EST 
When FormColors initializes it creates some colors for it's own use based on the system colors. There is no listener for changes in system colors so these colors are not updated when the system colors change. This is unlikely to change for Eclipse 3.7.
Comment 3 Miles Parker CLA 2011-02-02 01:53:47 EST 
Do you mean there is no listener in the SWT or in Forms? Because I know the view titles change immediately. Again this is completely a trivial issue..but one of those things that users do notice FWIW.
Comment 4 Chris Goldthorpe CLA 2011-02-02 13:05:55 EST 
SWT probably does have a listener, I don't think that UI forms has one, I could not find any code in the FormToolkit class that would react to palette changes.
Comment 5 Lars Vogel CLA 2019-09-24 13:57:36 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.