| Summary: | [RenderingEngine] Changing Side of Toolbars at runtime in the model does not update the application | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | UI | Assignee: | Missing name Mising name <Rene.Brandstetter> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | emoffatt, Lars.Vogel, nobody, tom.schindl |
| Version: | 4.2.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Lars Vogel
This is a good one...we have a variety of issues in the model's definition of TrimBars, notably that the model allows more than one bar on a side (and allows a bar to switch sides...;-). I sort of like the idea of being able to define multiple 'top' bars since it gives an alternative to the current layout that may be better for some apps). While the ability to change the side of an existing TrimBar is rarer it's still the right thing to do... In order to fix this we'd first have to provide the support for multiple TrimBars on a side; otherwise we end up with a very complex system (i.e. you can't change the side to 'RIGHT' if there's already one there...). Sounds good. I haven't thought about multiple Trimbars but this makes sense. @Sopot: is this fixed with Bug 376254 too? Not sure but getting rid of 'processHierarchy' sounds like a good idea to me..;-). Yeah I have lost the branch with that patch so I cannot quickly try it. I'll have to repatch to test it. I'm not too optimistic though. Not fixed with before-mentioned patch. 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. If the bug is still relevant, please remove the stalebug whiteboard tag. |