How do I get hotkey binding to show up on custom menu item?

[jrowell_fx]

I am able (in python) to create a custom menu item in the "File" menu that calls one of my python functions.

I am able to get everything loaded up properly through userSetup.py as well. (This is in maya2009 btw).

I can also make a hotkey shortcut so that I can call this same function - however...

For the life of me - I can not figure out how to get the hotkey binding to show up next to my new custom menu entry in the file menu!

Can anyone help me with this?

I will include (below) the various python commands that I use to make this happen - however I'm missing something obviously. For example, if I open the Hotkey Editor GUI I can not see my command under the "File" Category - not sure how to make it show up there - nor if it is even necessary. There is a MEL command called runtimeCommand() that allows you to specify a "category" - but python doesn't have that corresponding command in maya.cmds. Clearly assigning hotkeys to menu items in the "Hotkey Editor" makes the hotkey show up next to the menu item - so there is a way to bind these things together - I just can't figure it out.

Here's what I've done so far - in a file called menuStuff.py:

def fileMenuAdditions() :
gMainFileMenu = mel.eval("$tmp=$gMainFileMenu;")
mel.eval("buildFileMenu()")
menuList = cmds.menu(gMainFileMenu, query=True, itemArray=True)
if (not "savePlusPlusFileMenu" in menuList) :
cmds.setParent(gMainFileMenu, menu=True)
cmds.menuItem("savePlusPlusFileMenu",
label="Save ++",
annotation="Increments the file version - then saves the scene",
command="menuStuff.savePlusPlus()",
insertAfter=menuList[6])
cmds.setParent("..", menu=True)

cmds.nameCommand('savePlusPlusNameCmd', ann="Save++", stp='python', c='menuStuff.savePlusPlus()')
cmds.hotkey(k='S', ctl=True, name='savePlusPlusNameCmd')

def savePlusPlus() :
# You know - saves the file and stuff.

....and here's the contents of userSetup.py:

import maya.cmds as cmds
import maya.mel as mel
import sys
import menuStuff

cmds.evalDeferred("menuStuff.fileMenuAdditions()", lowestPriority=True)

That's all for now - I'm not sure what the best forums are to post questions like this - the Autodesk "The Area" forums don't seem super active, so I think it's between this one and CGtalk, unless anyone can suggest another great active maya forum.

[joojaa]

,>> There is a MEL command called runtimeCommand() that allows you to
specify a "category"

Thats simply because runtime commands are a feature of the mel language, python doesn't have runtime commands hence can not have a command for making them. So a runtime command would only work in mel intrepretter so not much point in exposing it to python users.

Python doesnt replace mel, everything thets been made in mel is totally oblivious to python. Python is and will be a second class citizen until all mel has been replaced with python. You still need to know mel because your working with mel trough python.

nor if it is even necessary.

Its not, however your users might appreciate this on the long run. But since you dont have any problems cluttering the mel workspace with mel.evals i dont understand what exactly is your problem use mel,eval since thats what your doing mostly anyway. Tough do yourself  a favor roll it all into one mel proc, its easier on you.

Your code is extremely ugly, theres a easier way to do this but i dont have time to teach you everything so ill just say change line:

cmds.menuItem("savePlusPlusFileMenu",
label="Save ++",
annotation="Increments the file version - then saves the scene",
command="menuStuff.savePlusPlus()",
insertAfter=menuList[6])

to:

cmds.menuItem("savePlusPlusFileMenu",
label="Save ++",
annotation="Increments the file version - then saves the scene",
shiftModifier=True,
ctrlModifier=True,
keyEquivalent="s",
command="menuStuff.savePlusPlus()",
insertAfter=menuList[6])

But one thing you could fix is remove the

import maya.cmds as cmds

import maya.mel as mel

import sys

from the userSetup.py and move the imports to each module. It breaks all the rules of python discovery. Sure it saves you 1-2 lines here and there but you also loose on portability and encapsulation. Worse you open yourself for a number of very hard to debug issues.

PS: he reason thet theres not much traffic is because people are busy working, the climate we are in right now doesnt make for the best grounds for helping new upstarts into a business when you yourself are hurting. So why halp train yoru own replacement?

[jrowell_fx]

Joojaa - I appreciate your help but you are very insulting and presumptuous on a number of levels.

First - that’s a simple solution to my problem - thank you. I didn’t read through all the arguments to “menuItem” and in all my numerous searches I never used the term “modifier key” I only ever searched for “hotkey” so unfortunately I didn’t stumble upon this. Too bad - I would have liked to have avoided your insults.

I don’t know who you are - and you don’t know who I am, but I’m almost positive I’ve been doing this for a whole lot longer than you, probably since when you were playing in the sandbox with your mom wiping your nose.

As for my ugly code - when I pasted my code into the text window here, it looked nice, but when I submitted my post it reformatted everything. You should have been able to guess that since python code doesn’t work without being indented - I obviously didn’t write it that way - so you aren’t as clever as you think you are.

Secondly I don’t need to be lectured by you on whether I should use MEL or not - I’ve used MEL for many years - probably since well before you even knew what maya was - and it’s an abomination of a language. You have to jump through hoops sometimes to do the simplest of things. I’m grateful for python being in maya - second class citizen or not, it’s a vast improvement upon MEL. As for “cluttering” my code with mel.evals - huh? Who cares? You gotta do what you gotta do sometimes - you make it sound like some kind of moral issue - get off your high-horse. This is the first time I’ve ever bothered to write GUI code - so this part of Mel/Python is new to me. If you have a suggestion for how I can make those calls I did without “mel.eval()” I’m all ears, otherwise keep your bitterness to yourself.

You owe me an apology. You should seriously consider giving me one - it’s possible that someday I’ll be interviewing you for a job - but you’ll probably be the one looking for the job - this is a small industry, and like I say, I’ve been here for a long time and know a lot of people. As for helping out “new upstarts” if you don’t want to help then get off this forum and spare us your condescension.

[thnkr]

Well you can always count on Jooja to tell you how much you suck

I don't understand why you make it so complicated. To add a menuItem for a python command, first create a runTimeCommand , like this:

runTimeCommand
    -annotation "Print \"Hello, world\""
    -category "File"
    -commandLanguage "python"
    -command ("print 'Hello, world'")
    MDcommand;

to add MDcommand to the File menu, do this

setParent -m $gMainFileMenu;
                menuItem -label ("MDcommand")
                        -annotation (getRunTimeCommandAnnotation("MDcommand"))
                        -command ("MDcommand") MDcommandItem;

Then assign the key.

I've got the impression that Maya sometimes messes up the commandLanguage setting for a runTimeCommand and changes it to mel again in the userRunTimeCommands.mel file. If so, change the command to python("something") (look at ArchiveScene for an example) or fix the file itself.

[jrowell_fx]

Hi Michiel

Interesting idea - perhaps have the code that modifies the menu item be mel - but have it call my python code - which is the important thing to be writing in python anyway, not the part that adds stuff to menus.

The reason it seems complicated is that I think you need to do all those steps in maya2009+ to add stuff to the menu items via the usersetup files.

Anyway, I think if I do it along the lines you suggest - my additions might play more nicely with the hotkey editor - As it stands my current setup is not working smoothly with it.

[joojaa]

I was criticizing your python structure not formatting. So wherever it looked like when you pasted it was still ugly. Yes i understand sometimes you gotta do what you got to do. However just because it works doesnt make it the best of things. Since you were quite obviously only interested in getting it working then that was what I told you to do.

And excuse me the code you have truly is ugly. I have no time to mother you around sorry. Sucks, I probably should, but I have nor the energy or time. .

• probably since well before you even knew what maya was

If you worked on maya 1.0 beta or alpha then yes. Tough to be honest it took me to maya 1.5-2 to fully migrate.

In any case if your interested in elegant way to do all your menu additions now and in the future in python and in mel and ready to do some learning give me a holler.

but you’ll probably be the one looking for the job

Theres a reason why people get moved to management. Even if there isnt a techical one it usually manifests itself sooner or later. You may well be becoming a bit rusty you know its nothing to be ashamed of we all have this. I personally suck far more at code than you ever will, the difference is im painfully aware of the fact

PS: We dont work on the same continent or business sector.

[joojaa]

Yes everybody sucks. question is how to suck less. Hearing it sucks is the first step to remedy. Knowing somethin sucks doesnt mean that it needs to be changed, just that it probably ought to.

userRunTimeCommands.mel file.

Yes i believe thats a known bug, its been reported.

[jrowell_fx]

Again Joojaa - you are astoundingly presumptuous - you have so little idea about what you're talking about. Why don't you stick to telling us about what you do know, like how to write nice menu code. Leave the demeaning comments about mothering people, and assumptions about who or what they are out of it, because it just makes you look the fool. But like you, I have neither the time nor the energy to father you and teach you some manners, as much as you are sorely in need of it.

Your signature should be "Slightly Helpful Troll" - you might want to consider this if you "want to suck less".

[joojaa]

LOL Ok, before we begin i need to know how your studios structure is to be set up.

Do you need a user enforcing system, where superiors ebforce what uers can and cant do and dictate. Or would you prefeer a user oriented system. So in essence do you need a tool for TD's only and lock normal users off or do you think users own their work environment.

This is a important question so i know where to start looking into. If you want open ill guide you to develop a menu manager and put it in the prefs just like the hotkey editor. If not then its gets a bit simpler to do but harder to do stuff.

[jrowell_fx]

Thank you very much Joojaa for the kind offer to help get a proper menu system going, but I'm going to pass on your offer to help for now. Ok - all's well that ends well - no hard feelings. Take care and thanks again for the help.