Hello friends
Hello friends,
Recently we've got a request to introduce a shortcut to move items to the first/last position on the current level of hierarchy: https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
And this bring me to a thought to use the current shortcut (Ctrl+Home/Ctrl+End) for this purpose. But with an extension - if an item is already on the top position on the current hierarchy level, Ctrl+Home would move item one level up (and put it at the beginning of this level).
This will break the current behaviour (moving item to the beginning of the list), but probably will make this shortcut more useful.
What do you think?
https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
Recently we've got a request to introduce a shortcut to move items to the first/last position on the current level of hierarchy: https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
And this bring me to a thought to use the current shortcut (Ctrl+Home/Ctrl+End) for this purpose. But with an extension - if an item is already on the top position on the current hierarchy level, Ctrl+Home would move item one level up (and put it at the beginning of this level).
This will break the current behaviour (moving item to the beginning of the list), but probably will make this shortcut more useful.
What do you think?
https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
Personally I agree with your suggestion Kirill.
ReplyDeleteI don't find the current behaviour at all useful.
It feels right that movement of an item should first be within it's siblings' level and then moving up levels in the hierarchy
Yes, like the idea. I never use Ctrl+Home in its current form, but definitely would with this change.
ReplyDeleteI've only "used" the shortcut's current functionality by accident, and was then left wondering where the task went.
ReplyDeleteAt least with the proposed change, it won't take so long for me to get the task back where I want it when I accidentally hit that keyboard shortcut in the future ;)
Sol M I'm with you - to me, Ctrl+Home and Ctrl+End are for NAVIGATION not moving something. I obviously haven't tried to go to the end of a list, but if I did, I'd use Ctrl+End to get to the bottom - and then be angry that things got rearranged.
ReplyDeleteSince Shift is used to indicate that we want to MOVE an item, the intuitive means would be Shift+Ctrl+Home and Shift+Ctrl+End.
And since we're in heirarchies and could be deep in them...the first use of ctrl+home or ctrl+end would either navigate the cursor or move the item to the first or last position AT THAT LEVEL, and if used again, then to the top or bottom of the next level up. Repeated use of Ctrl+Home will bounce us up to the successive parent levels.
That would be, to me, elegant and intuitive.
Ctrl+Home: go to first item at that level, if at first item, go to first item at the parent level.
Shift+Ctrl+Home: move item to the first entry at that level, if already the first item, then move it to the first item of the parent
I am happy to see an activity regarding navigating/moving the hierarchical structure.
ReplyDeleteThe current Ctrl+End is somewhat useful to me. It does not move items to the end of "the list", however, but to the end of whatever part of the list is displayed (because of hoist/focus).
Changing Ctrl+Home/Ctrl+End the way Kirill Maximov proposes makes sense to me. Two modifications: (1) When moving up one level with Ctrl+Home, I wouldn't want it at the beginning of the level, but right before the parent. A second Ctrl+Home would move it to the beginning of that level. (2) When an item is already at the end of a branch, Ctrl+End could continue doing what it is doing now.
Leslie P has a point. Ctrl currently means "move" for Up/Down/Home/End, it should probably stay that way. I guess using Home/End without modifiers in a way that is consistent with the new semantics suffices for navigation.
Please make sure that the new Ctrl+Home/Ctrl+End work with multiple selections. Which needs some additional thoughts.
Side note: Because tasks that were added via e-mail or using the bookmarklet appear at the top of a list, I would want a shortcut to move them inside the next subtree. Which is somehow the reverse operation of the new Ctrl+Home if an item already is on the top position of a level.
Thank you very much for your comments.
ReplyDeleteI hope to make modifications in Ctrl+Home/End behaviour and will post an update here.
By the way, Home/End should already move selection to the Home/End of the list. I'm not yet sure whether to apply the new behaviour to this shortcut as well. Personally, I use Home pretty often to go to the beginning of the list (and End the same way), and I'm not sure if this have to be changed, though it may be inconsistent with Ctrl+ behaviour.
Is it possible to provide alternate key combinations for the Mac?
ReplyDeleteNeill Cohen On a Mac, you can move items up/down with Cmd+Up/Down, and to the beginning/end of the list with Cmd+Home/End (in fact, this is like Fn+Cmd+Left and Fn+Cmd+Right).
ReplyDeleteHello, everyone.
ReplyDeleteI've finally dug out this task from my ASAP list and implemented it in a slightly new form (at https://beta.checkvist.com).
So, now it is possible to move selected task to the top/bottom position under the same parent. Also, it is possible to move the selected task before its parent (with the same shortcut).
As a shortcut, use Ctrl+PageUp/PageDown Alt+PageUp/PageDown on windows, Fn+Cmd+Up/Fn+Cmd+Down on Macs (if you don't have PageUp/PageDown keys).
Should work with multiple selected items as well.
Please check it out and let me know.
Thanks!
In Chrome on Windows CTRL-PageUp/Down is the shortcuts for switching tabs so this does not work for me.
ReplyDeleteI've tried using an extension to disable Chrome's behaviour but no joy.
Any ideas how I can get it working?
Hello Mark Dickens, shame on me. Please try Alt+PageUp/PageDown, you're right, Chrome block Ctrl+PageUp.
ReplyDeleteHi Kirill Maximov just tried it ... 'tis a thing of beauty, ship it!
ReplyDeleteThank you!
This is very, very useful for me. Thanks. Two thoughts: Alt+PageDown at the end of a level could move the item right after the sublist, symmetric to what Alt+PageUp does at the top. It would be the same as Shift-Tab, but easier to move items further down by repeating Alt+PageDown. And it would be great if there was in inverse to Alt+PageUp at the top of a sublist, i. e. move an item one level down to the top. I need this really often. (Could be one by Ctrl+Down Tab Alt+PageUp now, but it could be smoother.)
ReplyDeleteHello Ralf Hauber ,
ReplyDeleteThanks a lot for your comments, but I think this makes thing a bit overcomplicated.
For the first suggestion, to move things further down you can use Ctrl+Down at the end of the level (as it goes down on the same level, if needed). Also, I think that Shift+Tab is a good alternative here as well, as you already noticed.
For the second suggestion - this will make behaviour a bit unstable, because the idea is to move item at the end on the same level. The following case become contradictory for Alt+PageDown behaviour in this case:
- selected item
- parent
- child
- child
- another item
Alt+PageDown should move the selected item below 'another item', but you suggest to move it down the 'parent'.
I think for this case Ctrl+X/Ctrl+V on 'parent' should work nicely.
Thanks again,
Ad 1) Going beyond the sublist: Repeated Alt+PageUp moves an item to the top in a very convenient way („bubbeling up“ reflects the hierarchy). The same should be possible with Alt+PageDown. (Ctrl+Down ist good when staying on the same level of expanded sublists; not when navigating through hierarchy. Yes, Shift+Tab is a good alternative, but alternating keystrokes Alt+PageDown and Shift+Tab is too much exercise for my fingers.)
ReplyDeleteAd 2) Moving inside a sublist: I didn't mean to use Alt+PageDown for this. It would indeed be confusing. Cut and Past is a good alternative if the sublist is expanded. Otherwise it's two extra key strokes. Compare that to pressing Tab on an item below a sublist: it expands the sublist if needed, and puts the item at the bottom. I'm missing the very same thing for the top of the sublist.
Ad 1) Played more with it. Shift-Tab is ok. Just missing some consistency in behavior (Ctrl+Up and Ctrl+Down can be repeated beyond the parent, Alt+PageUp can be repeated beyond the parent, Alt+PageDown can't).
ReplyDeleteThinking about the keys, for me something like Alt+Up/Down would be easier to be used together with Ctrl+Up/Down when moving items. Especially when working on different (mobile) keyboards where the PageUp/PageDown keys are second class citizens and differently laid out.
Ralf Hauber Looks like the idea with implementing Alt+PageUp to move element outside the parent is good, but the shortcut is bad. We discussed the behaviour with Sasha and we'd like to try another approach - rework Ctrl+Up/Down to go through opened items one by one, regardless level.
ReplyDeleteI.e. Alt+PageUp/PageDown will work as initially suggested, like home/end on the same level under same parent.
But Ctrl+Up/Down will work across all opened nodes, without limitation to stay on the same level while moving. I.e. you'll be able to move element before parent with Ctrl+Up (when it is on the first position), and Ctrl+Down will go down to the subnote if it is expanded.
I'm not sure I explained it well. We'll try to implement and test this behaviour on beta.