Thanks everyone for trying XFORM, I appreciate the responses!
Stekler:
You need to unzip XFORM.ZIP into the ZPlugs folder found within the ZStartup folder. If there is no ZPlugs folder within the ZStartup folder, then you must create the ZPlugs folder first, then unzip XFORM.ZIP into your newly created ZPlugs folder.
At startup, ZBrush looks for a ZPlugs folder and if it finds one, it then loads any plugin files stored there (type .zsc).
Anatom:
Thanks for the feedback. In the next update I might try some version of what you suggest. In the meantime, let me say:
ZScripts cannot change the color or intensity of any buttons. However there are several alternative methods to indicate which button has been pressed including disabling the pressed button which makes it grey out, leaving the other two buttons available for pressing. I might do something like that.
In the case of the “u” button, I couldn’t very well disable it after being pressed, since it wouldn’t toggle anymore.
The current XFORM solution to these problems:
-
The color coding of the background (red=move, green=scale, blue=rotate) is supplemented by the little vertical label that changes between “move”, “scale” and “rotate” depending on which button was pressed. I hoped the color and the label would be enough to indicate the selected mode.
-
The “u” button displays a popup prompt each time it is pressed to tell you if uniform scaling is on or off. Also, if you REPRESS the Scale Button after you are already in scaling mode, this forces the popup prompt telling the current state of the “u” button - i.e. if uniform scaling is in effect or not.
As for implementing a Control+Click operation - (if I understand you) - that is a problem since the Control+Click is already used for masking operations.
As for using XFORM to edit a Previewed ZSphere Model? That’s an interesting find… Thanks for the tip!
Sven