"Expand to Level" should respect context like e.

"Expand to Level" should respect context like e. g. "Export" does. Example: When tasks are selected, EX exports only those. When nothing is selected (ESC), then EX exports the whole list. "Expand to Level" should work the same way, and not always expand/collapse the whole list.

Comments

  1. Kirill Maximov (KIR)6 December 2015 at 11:05

    Hello Ralf,

    Thanks a lot for the idea, it is quite reasonable. I've added it to the uservoice: http://checkvist.uservoice.com/forums/2121-general/suggestions/10986018-expand-collapse-to-level-or-branch-should-consider, for the record.

    Don't promise a quick implementation, though.

    Best,

    ReplyDelete
  2. Ralf Hauber7 December 2015 at 06:27

    No promise expected. I have seen you strive to provide a consistent UX. And you're doing good.

    ReplyDelete

Post a Comment

Popular posts from this blog

Any Toggl users here?

Any Toggl users here? I'm putting together an integration so the toggl (Chrome extension) button ( https://github.com/toggl/toggl-button ) is displayed for tasks on a Checkvist list. It's dead simple (a few lines of javascript), but I'm slightly torn on the best way to handle one aspect: whether or not toggl is shown for a particular list. It can't be always-on, as it adds too much clutter for non-projecty lists (who wants a timer button for the carrots on their grocery list?). What I have now is that if any task on a list is tagged #toggl, then all tasks on that list will have the toggl button. A few alternatives I canvassed were: - display toggl buttons only on subtasks of a task tagged with #toggl - display toggl buttons only on focused (hoisted) tasks - find some other way to indicate that all of a list's tasks should have the button, eg. something encoded in the list's name I think what I have now is the most convenient of these (I don't want to hav...
Read more