I poked around a bit but didn't find this discussed (which of course doesn't mean it hasn't been done):

I poked around a bit but didn't find this discussed (which of course doesn't mean it hasn't been done):

Why does 'un-hoisting/focusing' result in the list returning focus to the root level of the list (albeit, with the branch I had just had hoisted)? In the attached images, #1 shows the fully expanded list, #2 hoists Root_item_1, #3 hoists sub_item_1, and #4 unhoists sub_item_1. Notice that the focus has return to the root level.

It seems far more intuitive to me that if I press 'shift-right arrow' to focus that sublist, then 'shift-left arrow' should return the focus to the previous state.

Was this a deliberate design decision, and if so, what was the rationale behind it? I like to keep the focus well below the root level in order to keep things neat and uncluttered, and I find this hoisting logic a bit disruptive since it basically forces me back to root.



Comments

  1. Ralf Hauber13 March 2017 at 15:30

    Paul Garaud I once needed the behavior you describe. It's possible to show the parent list items to directly navigate to any level. In general, it would be nice to have a "back" when unfocussing. (But I also want to be able to get back to root in one step.)

    ReplyDelete
  2. Kirill Maximov (KIR)17 March 2017 at 10:20

    Ralf Hauber Paul Garaud Thanks a lot for the comments. I suppose we'll implement an approach when unfocus will work as focus UNDO, i.e. it will return to the previous focused state. Looks like it is not very hard to do, will add it the the next release pool.

    Thanks again,

    ReplyDelete
  3. Kirill Maximov (KIR)29 June 2018 at 08:44

    Hello, just in case, this "undo" behaviour has been implemented, thanks again for the idea: plus.google.com - 4 - Thursday update: Header styling and step-by-step unfocus It rains over ...

    ReplyDelete
  4. Kirill Maximov (KIR)9 January 2019 at 11:56

    Hello, regarding Shift+Left/Shift+Right behaviour, could you please comment on this topic in our new forum?

    discuss.checkvist.com - Un-hoisting / un-focus should move to next level up, not root - Checkvist Friends

    Would appreciate your opinion, thanks!

    ReplyDelete

Post a Comment

Popular posts from this blog

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
Read more

Hello friends!

Hello friends! I'd like to ask for your opinion regarding multi-line text editing. This suggestion comes from one of our Russian-speaking customers Dolina Zamkova so here is a translated abstract of our email conversation. Current problem: When you write multi-line text, you must press 'Shift-Enter' first, then use 'Enter' to start a new line, then 'Ctrl-Enter' to submit the text. Wouldn't it be easier to have a setting that will allow using Enter to always write multi-line texts, and always submit on 'Ctrl-Enter', like you do it in text messengers? So we could add a new account-wide setting, on the Settings page: () Finish editing by pressing 'Ctrl-Enter' (convenient for multi-line text) What do you think? Do you write multi-line texts in Checkvist at all? Other thoughts of how we could make it better? :)
Read more

I'm really enjoy using checkvist, you are adding great features very quickly.

I'm really enjoy using checkvist, you are adding great features very quickly.  What I feel is missing is more use cases.  How are people using Checkvist?  What are some recommend workflows?  How many lists do you have? User Stories will not only help those of use already using Checkvist to be more effective, but attract more non-technical customers. I like to keep my lists at a minimum.  I only split out for sharing but I'd prefer not to. Here are my lists: * Inbox:  This is where zapier based integrations go.  I have Jira tickets and emails tagged with "!action" going to list which I process daily. * The List:  This is my primary list.  Everything is here.  I use sub-nodes for different areas. * Honey Do:  This is the list my wife and I share to make sure we know what we both want done around the house. * "Client Project" - I have a few Lists I share with clients (Free lance web developer). I"m looking to write a more detailed blog post. How are your l
Read more