Community
Participate
Working Groups
During one of our chats with Susan there was an idea to make whole row (section) of commands more visible on hover. See the picture attached below.
Created attachment 208726 [details] The tree repo page with lots of commands You can see that it is hard to read this page. I know that we are going to get rid of tree navigators, but this "hard to read" issue may be valid on our new flat layout pages. If we could make whole rows/sections more visible on hover it might help. And I am not saying that not hovered rows should be grey (someone was complaining about disabled-looking commands), I think more about subtle distinction of hovered rows.
I thought the point was that they need to be visible because touch displays have no "hover". I might be misunderstanding the suggestion. I would be tempted to wait and see how it looks in the flat layout. Maybe with a bit of extra spacing around the buttons it wouldn't be bad for them to be always visible. By the way I really like the big new buttons with both icons and text!
I may have misunderstood what Szymon was saying when we were chatting. I thought he was suggesting some kind of highlight across the whole row to let you know where you are. The hard part about this is when your mouse moves off the row to go into the actions menu, the hover disappears yet you are still "conceptually" focused on that row. So I'm not sure. Note that I assume this tree repo is going away so I don't think we should optimize for this case. If we had to keep it for some reason I would want to make the rows taller just to give breathing room.
(In reply to comment #3) > I may have misunderstood what Szymon was saying when we were chatting. I > thought he was suggesting some kind of highlight across the whole row to let > you know where you are. Right, highlighting across the whole row or something what makes the row more visible. As I wrote in comment 1, this is mostly an issue in trees.
The original example (the trees full of various commands) is no longer valid, but the idea is still a sound one. Retitling bug to reflect this.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
