Community
Participate
Working Groups
I was playing around a bit and noticed that you could change the order of tabs in a tab group by using drag and drop on the tab. I also noticed that there is a Move>Tab Group option from the titlebar menu. Choosing to do so will revert the tab group to the default order.
This is happening due to a combination of two recent changes: 1. PartStack objects are destroyed and recreated after each drag/drop. 2. Tab order is now managed by the presentation (rather than the workbench) Change 1 was necessary to get detached folders docking correctly. The problem could be solved in two ways: 1. Handle drags of folders within the workbench differently than drags from a detached window and try to keep PartStacks around wherever possible (this is how things worked in M7)... unfortunately, this will still reorder tabs when folders are detached. 2. Always recreate the folder, but initialize the new folder using the serialized form of the previous one. This is less efficient, but it should also work for detached windows (as long as the presentations are compatible).
Reassigning the last of Stefan's bugs.
Is this still a problem in 3.3? PW
Yes, it still happens.
Eric, were you looking at this as part of minimize/maximize? PW
No, (didn't even know it was a problem) but I'll take a look since I'm in that area anyway to optimize the min/max.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
