I would also vote for navigation with keystrokes within the current state 
of the tree.
When i press a key, i don't expect MLO to search withing the collapsed 
trees.

воскресенье, 30 июня 2013 г., 18:38:28 UTC+3 пользователь Gabe написал:
>
> Hi, I'm an existing user of the excellent MLO Light, and have been 
> spending a bit of time trying out MLO4, but have encountered a usability 
> issue with this newer version, with regard to navigating through the 
> outline using the keyboard. I'm wondering whether it is by design or not, 
> as I can't find an option to disable it. Thanks if anyone can help point me 
> to a setting I've overlooked! :)
>
> Let's say I press the A key repeatedly. As expected, it cycles through all 
> tasks that starts with the letter A, allowing me to quickly jump between 
> them.  However, it now drills down through collapsed subtasks that also 
> start with A means that a lot of completely irrelevant subtasks are 
> revealed, when I'm only pressing A to be able to quickly jump to another 
> task that I can see at the root level of the outline.
>
> For example:
>
>    - Some task
>    - A task starting with A
>    - Collapsed branch
>    - Some concealed subtask 
>    - Some other concealed subtask
>             - Some other concealed subtask
>                - Another subtask starting with A, that I don't need to 
>                see because its tree is collapsed.
>             - Another task starting with A
>
> So in an outline like the one above, I would expect that pressing A twice 
> would jump me first to "A task starting with A" and then to "Another task 
> starting with A". But instead the second keypress expands an irrelevant 
> branch that I have deliberately collapsed, and drills all the way down 
> because there is a task buried within it which starts with A.  So my nice, 
> compact manageable outline has suddenly been expanded to show a bunch of 
> distracting tasks that I don't need to see, simply because they start with 
> the same character. I can't see any advantage to this, as I would just use 
> the search box if I wanted to locate a specific string in a concealed 
> subtask.
>
> The beauty of an outliner of course is that you only see what you need to, 
> but this is compromised when keyboard navigation behaves in this way. I'll 
> make an analogy with Windows Explorer - if I were to press A in the Folders 
> pane, it would only cycle through visible folders that started with A, not 
> subfolders that were buried within other collapsed folders, as there would 
> be far too many to cycle through. The same is true when dealing with a very 
> large outline; it quickly becomes unmanageable to navigate in this way.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mylifeorganized.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to