Summary: | [JFace] JFace registries should fail when accessed from non-UI threads | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Kim Horne <eclipse> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | Tod_Creasey |
Version: | 3.0 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Kim Horne
2004-11-02 09:06:54 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? 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. |