| Summary: | [Contributions] Contributed Status toolbar is smaller than the default status toolbar, causing clipped controls | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Filip Wieladek <filip_wieladek> | ||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | gheorghe, Michael.Valenta, pwebster, remy.suen | ||||
| Version: | 3.6.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=330106 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Filip Wieladek
Created attachment 207644 [details]
Image showing the bug
Image showing the bug
I forgot to mention that the toolbars were working correctly with the old syntax which is described here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=330106 Eric, can you take a look at this? PW Adding Bogdan, apparently this is a known SWT defect which has already been addressed in 3.7. Not sure whether it's possible to back-port or not... Bog, could you point us to the SWT defect that this was fixed against ?? Looking closely at the image posted, it looks like this is a different bug than the one I was thinking of (which had to do with Cairo clipping problems). You could try running "export GDK_NATIVE_WINDOWS=true" in a terminal and then launching Eclipse to see if that makes a difference. (In reply to comment #5) > Looking closely at the image posted, it looks like this is a different bug than > the one I was thinking of (which had to do with Cairo clipping problems). > > You could try running "export GDK_NATIVE_WINDOWS=true" in a terminal and then > launching Eclipse to see if that makes a difference. Thanks for the response. I tried that, but I still get differently sized "bars" (which would indicate that I still get less vertical screen space). The bars seem to have a correct size on windows. Is this the right place for this issue? Is this issue being looked into? If not, we will have to use the old syntax which did not break the UI (In reply to comment #7) > Is this the right place for this issue? Is this issue being looked into? If > not, we will have to use the old syntax which did not break the UI Yes, this is the correct place. We believe the underlying problem is bug 183003 PW There is a patch in bug 366214 for getting the experimental trim contributions API to work in some more cases. 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. |