Radial Menus

Hello,

I was taking a look at the radial menu's for configuration. I have only glanced over that before now, but am now trying to get a better understanding.

From what I am seeing, it goes against how the rest of the UI works at a very basic level.
It appears that the menu's are not context sensitive, only the "Menuset" of the menu's are. I do not understand the reason for that.

Let me give a simple example.

When creating a new menu, you are given the option's for that menu to be "Splinevertex/ Vertex/ Edge/ Polygon/ Mesh or object", but, they will show and be active in any mode.
If you create a "Subobject" or "Generic" Menu, they also show in all modes, only the "menusets" are context sensitive.
So lets say I want to create a menu for the options of creating the various primitive objects(Box etc). I create an "Object menu", call it "Primitives", fill that menu with the "Object shortcut tools" ("Create Box" etc). I then place that menu on the "Main". What ever mode I am in, be it object/mesh or subobject, that new menu will always show, and it tools/functions are always active.

Why have the options for such as "Object menu" when it shows in all modes?

your doing it wrong than, since I got different menus for differnet component modes set up fine.

I got my pretty much setup like Mays where in object mode the shift+rmb menu, does object creation tools, than for each of the component tools I have it displaying modeling tools that apply for those components.

I also got the same set up on the control+rmb menu which I use all for advanced selection.

your doing it wrong than, since I got different menus for differnet component modes set up fine.

The setting I made for radial menu are correct given the available options.

I got my pretty much setup like Mays where in object mode the shift+rmb menu, does object creation tools, than for each of the component tools I have it displaying modeling tools that apply for those components.

Sound like you have created custom hotkeys for menu selections, which will bring up the "menusets" for that menu.

I was looking at setting up a radial menu, where on a (default) RMB brings up the menu that is context sensitive, not setting hotkeys for menusets.

(...)
I got my pretty much setup like Mays where in object mode the shift+rmb menu, does object creation tools
(...)
I also got the same set up on the control+rmb menu which I use all for advanced selection.

This is a fantastic tip! I was wondering if it was possible. I don't how I did this, but I didn't notice the "set hot-key" button until I read your post, so I had my "Main" radial menu literally cluttered with sub-menus. Now I can finally separate them to different menus under different keys. Man, customisation in NVil is POWERFUL.

@Steve it is senstitive to both, i got multiple menus each on different modifier keys plus mmb, that show different options depending on what component mode i am in.

You get this by creating a menu as a "Generic Menuset" in the new menu popup.

(...)
I got my pretty much setup like Mays where in object mode the shift+rmb menu, does object creation tools
(...)
I also got the same set up on the control+rmb menu which I use all for advanced selection.

This is a fantastic tip! I was wondering if it was possible. I don't how I did this, but I didn't notice the "set hot-key" button until I read your post, so I had my "Main" radial menu literally cluttered with sub-menus. Now I can finally separate them to different menus under different keys. Man, customisation in NVil is POWERFUL.

ya you can even skip the mouse button if you want, and have it appear when holding a certain key or combination of keys too.

Steve it is senstitive to both, 

No it is not.

You get this by creating a menu as a "Generic Menuset" in the new menu popup.

Please read my previous posts.

ay nvm i got you, you want individual named menus to all be on one key, and work on certain contexts, instead off creating a context sensitive menu set?


would be nice, but it only affect the workflow of creating radial menus, and not the actual usage of them once setup.

Steve, in your example, if you create a hotkey for your 'Primitives' menu, it will be context sensitive, that's why passerby didn't see the problem. But you put it into another radial menu so it is not activated directly. In this case, the program does not treat it as contextual because it has no contextual contents. If I make it contextual, you will just have an empty menu space there in other modes and that would be a space waste. So it's better to create a 'menu set' instead.

If I make it contextual, you will just have an empty menu space there in other modes and that would be a space waste.

That is a limitation of your implementation.

So it's better to create a 'menu set' instead.

That pushes all context sensitive tools/functions to a level down in the menu system.

I am still curious as to an answer for my original question:- Why have the options for such as "Object menu" when it shows in all modes?

would be nice, but it only affect the workflow of creating radial menus, and not the actual usage of them once setup.

Not sure as to how you came to that conclusion. It would make a big difference in possible usage.

Ah well, never mind.
The user I was creating this (possible) config for has decided against the programmes usage.

I am still curious about an answer to my my original question though.

Well, I don't want to answer but make it contextual instead.