Checking checks/unchecks all items...how about just the one I selected?
When I first pull up the interface when I'm about to commit some changes (whether via the context menu in the Object Explorer or just clicking into the SQL SC window), you list all changes and select them all by default. That's not a big deal. The problem is, if I try to uncheck one item (not the check box at the top of the list) you'll uncheck ALL items since they're ALL highlighted.
This isn't normal UI behavior. If I'm checking one checkbox, I mean to check that one checkbox, not everything selected, even if I have them all selected. It's like being in Windows Explorer, selecting a bunch of files then clicking one of those files...you don't expect ALL of those files to suddenly deselect (well they do but only because you're now looking at a single selection...the one you clicked). If you hold the shift-key down, it just toggles the one selection. If you don't, it still toggles selections...it removes all selections but the one you've selected.
You either need to make a click on a particular row affect that row only (just like if I select any other part of the row selects that row only) or you need to let it just toggle the checkbox if that's what I clicked.
It took me a second to figure out...I was amazed that someone would even think to make a single click on a single row affect an entire selection of rows...
Ken
shared this idea
Hello! We fixed the issue with weird checkbox behaviour quite a long time ago. If you’re still now happy with how selection works, could you please let us know?
-
Keith
commented
I think this is a bug. If I select one item to be committed I don't want to see any other items on the commit screen. This could lead to accidental commits. In Visual SourceSafe and SVN if you select a single file to be checked-in/committed then only that file is checked-in/committed. This is what you would expect to happen.
-
Ken
commented
As with other "smaller" issues, this is just a nuisance that adds time and slows things down. I've got to do a lot of clicking to first deselect the entire list then reselect the items I want. That's my problem...when things are introduced that don't improve existing functionality but instead go in the opposite direction, I've got a problem.
I use SQL Compare/Data Compare all the time and even though it prechecks everything that's new, this problem doesn't exist because nothing's highlighted from the get-go. I can just click here and there and pick and choose what I'm about to deploy.
-
Hello Ken,
This is kindof a bug. :-) Our internal issue number is SOC-1092.
All objects shouldn't be highlighted by default when you try to commit your changes. Therefore, the checkboxes would work as you would expect and checking 1 box would only check/uncheck that box.
The highlighting is nice because you can sort the columns by name, schema, etc. and multi-select using your mouse + the shift or ctrl key and then have a really quick way to check/uncheck multiple objects that you are interested in.
Does this sound like a good resolution?
Also, if you only want to commit tables, then you could right click on the tables directory in the Object Explorer and select commit. Even though everything is listed on the commit tab, only the tables will be selected. This also works for an individual object as well.
I hope this helps for now and I will update this posting when we start to fix the issue of all objects being highlighted by default.
Thank you!
Stephanie M. Herr :-)
SQL Source Control - Project Manager