Torn-off menus
Sometimes you need to use the commands hidden in several sub-menus several times in a row. In this case, it would be convenient to tear off these sub-menus and temporarily hang it over the viewport. As it is done in Maya or other programs.
Also a useful feature from Softimage. A middle button click on the menu restarts the last used tool from all its sub-menus.
25 Comments
I would kill for tearable menu's... hitting hotkeys repetitively for floating menus is repetitive. Going to headers and sub-menu's over and over again with mouse gymnastics also is hard. Tearable menu's are the most efficient and customizable way of repetitive workflows without the needs of hotkey memorization. The Quickmenu is not solution to that (too much work to make a full menu that's already technically made for you)
Also - it looks you do not fully understand what is PME and what it can. .
Simple " Detach Menu " not even close to all the advantages and customizations which gives PME.
And yes it's available same for 2.8.
* @forestgumpovu4 * There are many options to achieve the goal. Just sometimes you need to tear off the damn menu. I would like to have this opportunity )))
Too bad it's a paid addon.
* @-L0Lock- * Rly ?... 12 $ for such complex customization tool ..... Are you kidding ...
No matter the content, no matter the cost, there are always plenty people which simply cannot pay or don't want to. Students to begin with, simple hobbyists, and all the people who must count their cents at the end of the month.
* @-L0Lock- * " Box " Blender functionality is good enough for hobyists, beginers, students, etc. .Anyway I think it stiil only 12 $ - all this peoples pay for games on Steam of for new film in cinema, or for morning coffee and croissant way more than this 12 $).
If you adwanced user and looking for " something more " - you 100 % get money from working with Blender. And get money from CG is not amount of money where 12 $ matter ... If someone want to get money from Blender but don't want to pay for devs who make such a good things - he's just miserly.....
There is nothing to discuss.
* @forestgumpovu4 * Yeah, there's nothing to discuss here. We strongly disagree and it's off topic. Have a nice day.
How about
Quick Favorites+ I found THIS and it's look cool but I can't understand is it already implemented ( if yes - where it's in latest build) or rejected...Detached menu it's cool but it still menu with lot of items. So when user need only several different items from different menus - call
Quick Favoritesmenu or hold sameFavoritestab on N panel looks better solution.I first read "turn-off menu" :')
Yeah that would be cool.
In 3DS I often have some menus flying arround like this. E.g. the export menu, I often need to to several exports in a row, because I export different selections, or the same withngs with different settings.
Even if I close it when I'm done exporting, i'm gld I didn't had to click all those drop-down menus a hundred times in a minute.
* @-L0Lock- * I use this unattached menus for export/import in 3D Max sometimes when I need to do something repeatedly. But it just because in Max it's imposible to assign hotkey to some things and it have no any form of PIE menus.
Sure! But even with a hotkey or a pie menu, it's not always the fastest way to do something. Having torn-off menus in addition would give us more flexibility.
Yes please, maybe the developers should have a look at the tear off menus in Cinema 4D. They are awesome to very quickly customize the current working context. You constantly need a submenu of a submenu for something particle related while working on it? Just tear it out on its header. Simple close the torn off menu after completing the task. It does not disappear in its original location. So nothing destructive, easy to clean up.
Yes, options exist. But not really a temporary solution for something you do 50 times for just the next hour and NOT every day. Configuring Pie Menus or custom shortcuts or something is really not something you would want to use in this case.
So please, Blender got so good in the last few versions, just have an honest look at the tear off menus in Cinema 4D. They are an awesome idea and feel extremely natural and quick.
YES,YES,PLEASE Tear-Off and dockable.
So many times, I've been drawing in KRITA or Photoshop and I accidentally draw just offscreen. I grab the whole window instead of making a line. I will throw a fit if this happens while I'm drawing with the grease pencil!
This is why I don't like tear-off and dockable windows/panels. Maybe if there is a way to lock them, or only tear them off when I want to (Maya's menus are mostly the annoying kind, but they handle drop-downs well enough. There's a space at the top of each drop-down menu that will tear it off, and you can just close it when you're done, no need to dock it again).
* @Josephbburg * you don't have to tear them off and that wouldn't effect you.
* @Josephbburg * If I remember well, Krita's docks have locks.
Else u can use
Add ShortcutorPMEaddon for such often used actions.* @forestgumpovu4 *
I know that you can create shortcuts in Blender, thanks. But Iām not talking about shortcuts, but about tear-off menus that are useful in cases when creating shortcuts is inappropriate. For example, if you have a need to perform in a row 10-15-100 operations that are needed for a specific one-time appointment.
It's not a matter of choice. It would be great to have tear-off menus along with shortcuts. Do you agree?
* @borschberry * If you need to perform 10-15-100 operations, why not use Python?
* @Josephbburg * mainly because writing hundreds of characters through hundreds of keystrokes and the hours it takes to learn how to code python is a burn for an artist. Sometimes you want UI flexibility and accessibility to work repetitive work with less manual labour (less keystrokes, less mouse clicks, less study) A tearable menu saves keystrokes and mouse movement and clicks by exposing items to a short mouse over where you need them how you need them, without hiding them or calling them over and over with unnecessary keystrokes or long zig zag mouse movements.
* @Josephbburg * Your counterarguments sound strange to me. This is additional functionality that will add convenience to many users. There are many ways to achieve the desired result, why reject one of them, just by the fact that there is another way (especially since it is less convenient).
* @Andres Stephens - Trinumedia * Fair enough.. I will suggest, however, that you save much more time by using Python than you lose by learning it. More time than you could ever save with UI for the task you describe.
I personally hate the idea of tear-off menus, because I see them as a band-aid for bad design. It's far better to make frequently used operators accessible from a shortcut. If they aren't used frequently, but are often used together, they should have their own mode.
I want the option to be there, as long as I can turn it off so I never have to see it.
* @Josephbburg * I do code and yes, it helps.. but having to code functionality for a GUI to make your work easier is essentially redundant - you have to press and memorize hundreds of character combos and keystrokes to make a script (or copy paste and understand it). A UI needs mouseover designs, either customizable toolbars with all tool operators, or something that can be customized to show floating header entries (tear-able menus). Right now Blender has none other than hard learned hotkeys for hundreds of operators that you can't customize for mouseover in the interface other than a quick menu that is always hidden (all floating menus are hidden too, under keystrokes). There is a lack of mouseover workflows, and the new toolshelf of 2.8 is only a beginning to solve this.
An artist struggling with improving animation, sculpting, modeling, art and more shouldn't also need to learn how to hard code to be an artist. Just a thought. This is a topic about mouse over accessibility to operators for more efficient customized workflows, not just repetitive workflows.
* @Andres Stephens - Trinumedia * I agree, no one should have to learn how to code--some people just don't think like computers. I think the only place I disagree with you is how to solve the problem, but then, I'm not offering any solutions!