Bug 77476 - [JFace] JFace registries should fail when accessed from non-UI threads
Summary: [JFace] JFace registries should fail when accessed from non-UI threads
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-11-02 09:06 EST by Kim Horne CLA
Modified: 2019-09-06 16:09 EDT (History)
1 user (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 Kim Horne CLA 2004-11-02 09:06:54 EST 
Currently if a non-UI thread is the first to access a key in a JFace registry
that has not yet been realized bogus results will be returned.  Creation
requires the UI thread, so we're not creating - we're using the default
font/colour and failing silently.  This is bad.
Comment 1 Kim Horne CLA 2004-11-11 12:03:56 EST 
Other observations regarding displays in JFace:

the JFace registries (JFace as a whole) are only ever designed to work with one
Display.  Indeed, the registries returned by JFaceResources are no longer valid
after the display that initially created them is disposed.  It would be nice if
they could respond according to changes in Displays.  Ie:  Display one is
disposed, JFace no longer holds onto the old one.  When next elements are
requested it is hooked to the new display.

Is the solution here to have seperate registries (all backed by the same
configuration) for each display?
Comment 2 Susan McCourt CLA 2009-07-09 18:32:12 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:48 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.