ya when i have some time i cold rewrite your match procedure in python. also if you want to go aobut jump from mel to maya, you should prolly just use the maya.cmds and stick away from pymel, since useing maya.cmds is more similar to mel, since it allows a purely procedural scripting style like mel. pymel will force you…
ya not exactly what i was thinking but i found a other solution, and might script my own way to do that later on. havent had a chance to peek at your code yet but i find the match UV's quite slow compared to the same operation in UVdeulux, not sure if that is just due to the faster execution speed of python compared to mel…
Try executing this line of MEL code: windowPref -topLeftCorner 0 0 -widthHeight 1214 759 -parentMain true uvTextureEditor; NightshadeUVEditor; If that doesn't work: Open up the script editor, go to history and check all the 4 top checkboxes. Then go to edit > clear all and then type in NightshadeUVEditor in the bottom…
Well my UV Editor resides in the default window so if it's gone after minimizing then the most probable cause is that it's off-screen (common problem when you for example copy your preferences to a computer that has only one display.) You can try deleting the UV Editor window with the following line of MEL-code: deleteUI…
ya wasn't saying it is bad, just saying OO programming is quite different from procedural, and pymel forces you into it, while with maya.cmds it isn't object oriented, unless you build your own classes and objects. like i personally much prefer working with OOP concepts than not, which is why i have never went back to mel…
Brilliant little tool, many thanks to you! I've been using it all day :D Worked like a charm... up until just now when I minimized the NightShade UV Editor window and it's completely gone, nothing happens when I run "NightshadeUVEditor" in the MEL-script line or when I press the shelf-shortcut I created. Going to…
Thank you for your reply. Yes that issue with the stack UV shells -function was hotfixed a couple hours after I released v1.2. Download the zip again and things should be working as expected. Turns out one line of code had been deleted by mistake. Regarding exceptions: MEL has a command called "catch" that can be used on…
still would be nice for it to know via the UI of the uv tools. but the maya interface does notify you of the active tool, and if no tool is active gives you qucik access to the last used tool. @nightshade, your app should be able to check what the current active context is with the checkCtx command which is available in…
get a error when trying to stack shells in maya 2012 // Error: file: C:/Users/Chris/Documents/maya/2012-x64/scripts/textureWindowCreateToolBar.mel line 872: Cannot convert data of type string to type float[]. // this also uncovers something really bad when the program errors, when a operation starts you have the undo stack…
I'm afraid not but this is actually very easy to implement. I will definetly add it to my "todo"-list. Thanks! More sophisticated texel density tools will definetly be available in the future. Picking the average TD from a couple faces - that's a really cool idea. That will go to my "todo"-list as well, thanks! 1) Yes this…