That's simply to reduce the risk of another script overwriting the variable so we're clear. As far as the rest of the script goes - if it works you're good. There's not really enough code there to provoke any bugs.
Here’s my script so far. Can anyone make this more elegant/professional for me please? I think this will help alot of people who use wacoms in max. Also will be happy to credit anyone who helps with it in the script. All for the community folks. ( global selectionChanged callbacks.removescripts #selectionSetChanged…
Right, im being more ambitious with this now....can anyone find any issues with this? trying to get it working now properly with sub object mode. Also can anyone explain why this means? "ev nd" i have no idea, i just followed the maxscript reference. Ideally test this out with a wacom :) but woks fine with a mouse too.…
Is this is the whole script?@poopipe is right, you have to change the name of your global variables to be not so "obvious" and "common". At least use something like this:global selectionChanged_adj34wrff
When using a tablet it's so ridiculously easy to move an object by accident when trying to select it. This script makes sure you're always using the select object tool instead of move,rotate,scale. It's the same as pressing Q. But automates it everytime you make a selection.
You are welcome :) glad it's helping you. Please note though I've been looking into this for some time and I've concluded max just isn't great for wacom use. My script certainly helps but you need to make several workflow changes in order for it to be comfortable with a tablet