Community
Participate
Working Groups
Improvements in Synchronize view in recent 3.1m2 build make it more pleasant to work with "Commit Sets" feature. However it is still inconvenient to change layout and turn on/off "Commit Sets" together. It seems that it make sence to remember settings for "Commit Set" and layout between different modes. I usually use the following: -- Incoming: commit sets / flat (rarely I have to switch to compressed folders) -- Outgoung, In/Out, Conflicts: compressed folders It is still make more sence to me to have layout buttons (or combo drop-down) on a toolbar instead of previous/next buttons.
Will consider for M4.
We don't have time to address this in 3.1
Ca you at least add flat/tree/compressed to Syncronize toolbar?
No. For the reason why not, see bug 88144 which is a request to reduce the number of buttons in the sync view toolbar.
That can be resolved by replacing 4 buttons for in/out/inout/conflicts by a single one with a dropdown. Then you will have more then enough space for one more icon with a drop down.
Yes but there are some users who use those buttons. As I said in bug 88144, what we need is a way to customize what buttons appear in the toolbar. This will not happen for 3.1.
I'm not suggesting to remove it, but replace to more compact representation. Customization would be really nice. I'd love to get rid of those prev/next buttons for a long, long time. :-)
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.
