| Summary: | use <visibleWhen/> for contained components | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> | ||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.8 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 374326 | ||||||
| Bug Blocks: | 321278, 376368 | ||||||
| Attachments: |
|
||||||
|
Description
Steffen Pingel
Proposed change: http://review.mylyn.org/375 Paul Webster writes on bug 355059 comment 29: > You can ask the property tester to re-evaluate at any time using > org.eclipse.ui.services.IEvaluationService.requestEvaluation(String) > > The only other thing to be careful about is the property tester has been added > in your UI plugin. forcePluginActivation will allow the UI framework to load > any UI delegates it thinks it needs. I have committed the change. I tried using the evaluation service to trigger toggling of visibility on preference change but that didn't work. The workbench updates visibility on shell activation though which seems good enough. Created attachment 214364 [details]
mylyn/context/zip
Steffen, I installed 20120531-0157 and am not able to hide the trim. Changing the preference has no effect. Also, bootstrapping on master, changing the preference hides the trim but leaves behind an empty toolbar. (In reply to comment #4) > Steffen, I installed 20120531-0157 and am not able to hide the trim. Changing > the preference has no effect. I guess you can ignore this comment - I somehow have Mylyn 3.7.1 installed. Comment 5 still stands though. (In reply to comment #5) > Also, bootstrapping on master, changing the preference hides the trim but leaves > behind an empty toolbar. I have seen this, too, but couldn't come up with reliable steps to reproduce. Please file a platform bug if you are still experiencing this with RC4. This is reliably reproducable on 3.7. I have not seen it on 4.x. I posted a comment on bug 201589. |