https://bugs.documentfoundation.org/show_bug.cgi?id=147807
--- Comment #9 from Eyal Rozenberg <[email protected]> --- (In reply to Heiko Tietze from comment #7) > We have plenty of tickets regarding the Navigator UI. It's a typical > feature-creep example with overloaded functions and unclear use cases. I guess that must be it... > And > we cannot change it without making many users angry due to missing features. Well, I'm not suggesting adding or removing any features. But let me rephrase the two options I've suggested in light of the comments by Jim and yourself: 1. Add a label indicating that the top menubutton is "Navigate By" or "Search By"; and perhaps even add a separator between the top row and the rest of the window, to make it clear that the menubutton does not select a category. 2. Whenever the user clicks an item in the content tree, that item's category is also selected in the top menubutton, and vice-versa - when you select an item that's also a Category in that menubutton, it's selected also in the content tree. 3. Like option (2.), but partial: menubutton affects content tree selection but not vice-versa; that would make it easier to continue searching in the same way despite manually trying out specific items in the tree. Option (1.) really doesn't change any functionality. Options (2.) and (3.) change behavior, but you do not lose the ability to do anything you were doing before, nor gaining a new ability. -- You are receiving this mail because: You are the assignee for the bug.
