Possibly, but that could cause more confusion. In your example, rows 7, 12, 22, 30, 42 and 56, if moved up one would then become rows 6,7,8,9,10 and 11. That makes send for drag & drop as you are plucking them out and then inserting them into a specific place but for moving up/down a row at a time it doesn't make sense as the behaviour changes depending on if you move up or down eg what if you want to group them all from row 56 but move them up? What could make sense is a separate command to let you group all the selection at the first or last item in the selection. I might look into that down the line as it could be useful in cases similar to your example.
Thanks Martin On 28 Jul 2009, at 8:56 pm, Chris Blouch wrote: > Makes sense. So if I have four rows with A B C and D. I select rows > B and D and then hit shift option up I would now have rows B A D and > C. Hitting up again gives B D A and C. Is this what users would > expect? Normally I would think folks would be trying to cherry pick > rows they care about and drop them as a cluster somewhere. The > method you proposed sounds like it could get confusing quickly. Say > I want to move all my favorite songs to the top of a playlist from > random locations in a long list. I might pick rows 7, 12, 22, 30, 42 > and 56. To get them all to the top I would need to option up arrow a > bunch of times to sort of scrunch them all together at the top. What > if I wanted to put my second favorites after the previous 6 tracks. > Would I need to scrunch them at the top and then drag them down to > the 7th row? I guess I'm arguing that all the selected rows should > be inserted in the destination rather than interleaving. > > Hope this helps. > > CB > > Martin Pilkington wrote: >> >> Hi Chris, >> >> All rows get nudged up one space. When you reach the top or bottom of >> a table then they get nudged together. For example, if you have >> rows 2 >> and 4 selected and hit shift-option-up then the they will move up to >> be rows 1 and 3. Then if you hit shift-option-up again row 1 won't >> move as it is at the top but row 3 will, so they will now be rows 1 >> and 2. >> >> I have a sample application up at http://dropbox.mcubedsw.com/M3TableView.zip >> . As I said, once you have selected some rows you just hit shift- >> option and either the up or down arrow to shift the rows up or down. >> Hopefully it feels easier than current methods. >> >> Martin >> >> On 27 Jul 2009, at 10:05 pm, Chris Blouch wrote: >> >> >>> What happens if I have multiple discontiguous rows selected and I >>> option >>> up arrow? Do all the rows get inserted one row above where the top >>> selected row used to be? Probably the worst case scenario for >>> complexity >>> but something to consider. >>> >>> CB >>> >>> Martin Pilkington wrote: >>> >>>> Hi All, >>>> >>>> I haven't posted for a while so for those who don't remember me, my >>>> name is Martin and I'm a Mac software developer. I'm currently >>>> having >>>> a problem with making one of my applications accessible, but in an >>>> easy to use way. There is a lot of drag & drop functionality in my >>>> application. Some of it is easy, such as using copy and paste to >>>> get >>>> items from the library to the collections (like with putting songs >>>> into playlists in iTunes). However, some of it is hard, such as re- >>>> arranging items. You can do copy/cut and paste but this is a bit >>>> awkward. I've also been pointed to how to do drag & drop with voice >>>> over but to me that seems quite tedious. >>>> >>>> I believe I have a solution that seems to me like it would be a lot >>>> simpler, but I wanted to get the opinion of some blind users about >>>> whether they would find it more useful. The solution is that if you >>>> hold down the option key and press the up or down arrow keys, it >>>> will >>>> move the selected table rows up or down one place. To me it seems >>>> to >>>> be a better way to re-arrange items with a keyboard for all users, >>>> but >>>> the main aim of it is to improve accessibility. I will end up open >>>> sourcing any solution and pushing for other developers to include >>>> it >>>> in their applications so hopefully it can become some sort of a >>>> standard. >>>> >>>> Any thoughts anyone has would be much appreciated. >>>> >>>> Thanks >>>> >>>> Martin >>>> >>>> >> >> >> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en -~----------~----~----~----~------~----~------~--~---
