Community
Participate
Working Groups
the local toolbar still has the "Show change sets" button. The view's preferences have "Automatically Enable Commit Set Groupings in CVS synchronizations". These two things mean the same thing to me. what's the difference?
We changed the terminology in 3.1 to be "change sets" in order to generalize the support (i.e. commit was CVS specific). I have change the occurance of "commi set" to "change set".
The problem is that these two different toggles suggest the same thing to me. The one called "automatically ..." seems to do nothing at all. Even if I invoke a synchronize from the main toolbar. The other toggle on the local toolbar actually enables commit sets.
The synchronize view can have many pages. The preference indicates the default to use for new pages as they are added and the toolbar toggle changes it for the currently active page.
Ok, that's beyond the scope of an ordinary user. Pages are an implementation detail that the user doesn't know about. Page creation is random with respect to the user's synchronize operations (for example, if the perspective was closed or left open). The right (or at least consistent and not different) way to do this is the way JDT's outline pages work. For example, the "Sort Alphabetically" toggle changes the sorting for the current page only, *BUT ALSO* sets the default for pages opened in the future. Most users will not find this preference toggle.
Makes sense. No time for this in 3.1 though.
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.
