I have been using your script consistently for a while and it is great. Thanks for sharing it!
I was giving it a test run in Maya 2013 and wanted to report a few problems I had:
1) I get the following error message: // Error: file: D:/Maya/2013-x64/prefs/scripts/heLightControl.mel line 3348: Object 'allLightsTSL' not found. // This error is thrown in a few situations. First, if I run heLightControl and there are no lights in the scene it is thrown (it would be nice if a message popped up that said "There are no lights in the current scene"). Also, if I close the lightControl UI and then add another light to the scene the error occurs - it is almost like the script is still running in the background or something. If I add a light while the window is open the error doesn't occur. Try adding lights with the lightControl window open and closed and see what I mean.
2) The process of unifiedRenderGlobalsWindow; and then deleteUI unifiedRenderGlobalsWindow; in the heLightControl global procedure causes the render globals to appear, then dissapear (as I would expect it to). But this flicker across the screen sort of makes it look like something is wrong witht he launch of the tool and I am not sure why it is even necessary? Might want to check this out.
3) More of a suggestion - I would name the actual script the same name as the procudure that runs it. More of a measure of good practice. I would rename to "heLightControl.mel", remove the last line of the script "heLightControl;" and instruct people to type/add to their shelf/etc. "heLightControl();".
Again, thanks for the cool script and I look forward to the next update.
I have been using your script consistently for a while and it is great. Thanks for sharing it!
I was giving it a test run in Maya 2013 and wanted to report a few problems I had:
1) I get the following error message:
// Error: file: D:/Maya/2013-x64/prefs/scripts/heLightControl.mel line 3348: Object 'allLightsTSL' not found. //
This error is thrown in a few situations. First, if I run heLightControl and there are no lights in the scene it is thrown (it would be nice if a message popped up that said "There are no lights in the current scene"). Also, if I close the lightControl UI and then add another light to the scene the error occurs - it is almost like the script is still running in the background or something. If I add a light while the window is open the error doesn't occur. Try adding lights with the lightControl window open and closed and see what I mean.
2) The process of unifiedRenderGlobalsWindow; and then deleteUI unifiedRenderGlobalsWindow; in the heLightControl global procedure causes the render globals to appear, then dissapear (as I would expect it to). But this flicker across the screen sort of makes it look like something is wrong witht he launch of the tool and I am not sure why it is even necessary? Might want to check this out.
3) More of a suggestion - I would name the actual script the same name as the procudure that runs it. More of a measure of good practice. I would rename to "heLightControl.mel", remove the last line of the script "heLightControl;" and instruct people to type/add to their shelf/etc. "heLightControl();".
Again, thanks for the cool script and I look forward to the next update.
-Nick