Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[HPBEME]

Yes, lock/unlock tab is in the tab menu, but you can only access that for the active tab.  My request is RMB on any tab, active or inactive, to toggle between lock/unlock.  In addition, eliminating the need to navigate to a specific line in the menu (and occasionally selecting the wrong item) by simply right clicking the tab is far quicker and would be a really nice, yet simple, UI enhancement.

Doing this does not conflict with current behavior
- RMB Inactive Tab: nothing happens
- RMB Active Tab: context menu with 1 item "execute (tab name)" appears. Selecting that just brings up the tab menu - which already activates automatically by simply hovering over the tab - so this context menu has zero value.

I have a feeling this is something Matt could implement in the code in a matter of minutes.

[Matt]

Another option would be middle click so the right click menus could stay.

[lepa]

Middle click is generally used to close tabs and also MC has implemented middle click close although it doesn't always work

[Matt]

Well I'm not the biggest fan of switching right click.  Is there another way?

[lepa]

Agree with rmb, not a fan. Eventhough MC doesn't use it at all here it is usually used to open context menus. Could it be something like toggling with ctrl + lmb perhaps?

[HPBEME]

Please do not change the middle mouse button currently assigned to closing the tab.  MMB is used to close tabs in every single browser, and something I (and many others) make great use of. 

Middle click is generally used to close tabs and also MC has implemented middle click close although it doesn't always work

I've never had that issue. Works every time. If you MMB a tab that is locked, MC asks if you're sure you want to close it... Perfect.  It is the fact that middle click closes tabs, and my request that RMB toggle lock on/off that would make using them together so symbiotic.

Agree with rmb, not a fan. Eventhough MC doesn't use it at all here it is usually used to open context menus. Could it be something like toggling with ctrl + lmb perhaps?

MC already has many UI interactions that are nonstandard. 
- Hovering over the active tab brings up a menu - I have never seen that in any other other program
- Left clicking the tag window image brings up a context menu - completely nonstandard
- When that same image is shown at the bottom of the tree, you have to right-click to get the context menu - inconsistent behavior

I could list even more if I were so inclined, but that is not the point. MC has unique UI interactions just like every program, and that is not a bad thing. Users simply adapt.

That said, MMB to close tabs is commonplace in so many programs that it is not something you should ever change - right up there with cut/copy/paste. RMB for context menus also falls into that same category, but as noted above, MC already ignores that (at least for a specific portion of MC).  That MC typically honors RMB to show context menus is absolutely the right thing to do.  The only reason I think it's irrelevant here is that the active tab RMB context menu is of zero use - let's go through the steps shall we... 

- Bring cursor to active tab -> MC automatically shows tab context menu (completely nonstandard behavior, but one I've adapted to)
- right-click on active tab -> tab context menu disappears!
- select "execute…" -> tab context menu reappears!

So a user has to go through multiple steps, only to achieve the very thing that was there right off the bat. I find it impossible to believe anybody would continue to use such a method to bring up the tab menu after seeing what it does just once. And before markf explains to me that "I can't know how other people use the program"... just don't.

How about implementing it in the beta release and see if it causes an uproar?  To me, this change falls into the category of no-brainer.  In the future, for those who happen to RMB a tab will see that the lock icon disappears. A subsequent RMB and the lock icon returns.  The previously unknown/unexpected behavior becomes instantly recognizable and adopted.

This seems like it would be easy to implement just to see how it goes, but if it is a major undertaking, then by all means ignore this request.

[lepa]

I have much more stronger opinion on those non-standards (and that really weird play logic which plays everything even though you click items play...) you listed than this