Ludek wrote: ↑Thu Dec 19, 2019 11:16 am
I think that context menu is already quite overflowing, so adding another "Open in tab" context menu item would just make the situation worse.
Overflowing?
- the Media Tree node has only two entries in its context menu
- the sub-nodes do have have 9 entries ... but that is not so many ... items in the main panel have 23 entries, maybe I thought that I meant there?
Some of the existing 9 entries don't belong there IMO anyway
- why is the Track Properties option there? That is just a waste of space at that level.
- also why is AutoTag taking up one of the slots on sub-nodes like Music>Publisher? ... in the Media Tree? which should be all about UI navigation IMO ... ie. if it belongs in the Media Tree at all, it should logically be added to the lonely two entries at the top level for the Collection ... ie. there is no no special AutoTag operation for "Publishers"
- most of these other 9 entries should be at the top of the collection, not at the sub-node level IMO
Ludek wrote: ↑Thu Dec 19, 2019 11:16 am.
Ctrl+click is a standard behaviour for opening links in the new tab (in internet browsers) -- so I believe that it is sufficient.
Browsers also
have a context menu for urls, with a "open in a new" option .... this is my "standard" way of opening in a new tab. I didn't know the ctrl key behaviour.
You could improve upon the above example from Chrome, by advertising the Ctrl key behaviour in the context menu option ... that would help discoverability
Barry4679 wrote: ↑Tue Dec 17, 2019 8:23 pm
- I think the right click action could be more consistent ... in all of the places marked yellow, a right click does not invoke the click action, ie does not navigate, nor update the UI ... it just opens the right click menu ... but the red places do invoke the click action, ie. navigate
You did not address this point in your response.
You used a browser as an example ... try right clicking one of the non-displayed tabs in your Chrome browser ... that right click doesn't navigate to open that tab ... it just opens the context menu for the tab ... maybe I was only wanting to close the tab.
I think the MM5 Media Tree right click behaviour is also "wrong" ... browser's don't have something like a Media Tree, but try Word ... a right click doesn't navigate to the item that I click
I think that it it would be better if MM5 was consistent with itself, and other s/w products .. ie. a right click on a control opens the control's context menu ... it doesn't trigger UI navigation.