Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 381781

Summary:

trims change position when more than one is contributed

Product:

[Eclipse Project] Platform

Reporter:

Sam Davis <sam.davis>

Component:

Assignee:

Platform-UI-Inbox <Platform-UI-Inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

bsd, emoffatt, pwebster

Version:

4.2

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
screenshot	none

Description Sam Davis

2012-06-05 16:35:22 EDT

If I have the Mylyn active task trim enabled and also contribute a second trim using the following xml:

bc.. <extension point="org.eclipse.ui.menus">
	    <menuContribution locationURI="toolbar:org.eclipse.ui.trim.command2">
	      <toolbar id="org.eclipse.mylyn.tasks.ui.trim.container">
	        <control
	           class="com.tasktop.foo.FooTrim"
	           id="com.tasktop.foo.FooTrim">
		     </control>
	      </toolbar>
	    </menuContribution>
	</extension>
p. 

then the trims are in the top-left, below the toolbar, instead of the top-right. I'll attach a screenshot showing the difference.

Comment 1 Sam Davis

2012-06-05 16:36:24 EDT

Created attachment 216885 [details]
screenshot

Comment 2 Sam Davis

2012-06-05 16:40:09 EDT

Actually, I don't know if this is a defect. It happens because I'm contributing to the Mylyn trim, causing it to be too wide. If I specify a different toolbar id, then one trim is shown at the top right, and the other at the top left. In other words, it line wraps.

Comment 3 Steffen Pingel

2012-06-05 17:30:35 EDT

I have seen that, too. You can avoid the wrapping by removing toolbar contributions until there is enough space.

Comment 4 Lars Vogel

2019-11-14 03:38:47 EST

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.