| Summary: | [Compatibility] Cannot open views in 'Java Browsing' perspective | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Remy Suen <remy.suen> | ||||
| Component: | UI | Assignee: | Remy Suen <remy.suen> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Remy Suen <remy.suen> | ||||
| Severity: | major | ||||||
| Priority: | P3 | ||||||
| Version: | 1.0 | ||||||
| Target Milestone: | 4.1 M3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Remy Suen
There are two things wrong here. First, ModeledPageLayout creates (3.x) placeholder stacks by relying on the 'visible' feature instead of the 'toBeRendered' feature. Second, the EModelService's bringToTop(MUIElement) merely sets the element's 'toBeRendered' flag to 'true'. It should set the 'visible' flag to 'true' also. (In reply to comment #1) > Second, the EModelService's bringToTop(MUIElement) merely sets the element's > 'toBeRendered' flag to 'true'. It should set the 'visible' flag to 'true' also. <rcjsuen> emoffatt: Should EModelService's bringToTop method set 'visible' to true? <emoffatt> no...if the stack is minimized then bringing one of its parts 'to top' shouldn't put it back in the presentation <emoffatt> it's starting to appear as if the general rule is that 'visible' == false puts the control under whomever set it to false, the general code should *never* change it (at least I can't think of a case offhand where this makes sense) <emoffatt> it's up to the 'hijacking' code to ensure that everything still works :) Created attachment 181822 [details]
ModeledPageLayout patch v1
(In reply to comment #3) > Created an attachment (id=181822) [details] > ModeledPageLayout patch v1 Patch released to CVS HEAD. |