It only works on the selected part of the object.marcel wrote:Good tool for the workspace. It can be used as the shell tool of modelside. Is it possible to use it on a selected part of an object or is it allways on the entire object?
No, it would require a complete rewrite for modelside. Besides I think marcel showed in another post somewhere around here that the shell tool can be used as a normal move tool.bitkar wrote:hey, thats useful... is it possible to compile it as tsx for modeler (ts6.6) side?
Nice find! I can confirm that running that command works great in several test on my own. Thanks Clinton!clintonman wrote: I think i discovered a way to make the Watch Dog Event node work better. In this tool I run the Watch Dog Event manually the first time and that seems to "unstick" it so it works reliably. I'll need to do some more tests, but in the past it was unpredictable if the node was more than about 2 or 3 levels down in the scene graph. Hopefully this trick will fix those cases too.
Request is done.trueBlue wrote:Nice find! I can confirm that running that command works great in several test on my own. Thanks Clinton!clintonman wrote: I think i discovered a way to make the Watch Dog Event node work better. In this tool I run the Watch Dog Event manually the first time and that seems to "unstick" it so it works reliably. I'll need to do some more tests, but in the past it was unpredictable if the node was more than about 2 or 3 levels down in the scene graph. Hopefully this trick will fix those cases too.
Also me thinks that converting the selection to vertices would be good too!
Node.Value("/Preferences/Mesh Editor Settings", "PE selection mode") = "vertex"
MeshModifiers.ConvertSelection('','')
Even better if you could use the present PE selection method instead of only vertices.
Thanks for the suggestion. It's easier to just convert the selection back and forth, so that's what I did. 
No clue, without steps to reproduce it can't tell.trueBlue wrote: 14 Jan 2020, 18:40 Can you check out this widget?
I am getting an error when I open it in Widgets/Tools/PE NormalMove/silderReport
Capture.PNG
That would never happen in normal use. So if you want to fix it you'll have to add some tests to check for proper selection and that the selected object is in PE mode.trueBlue wrote: 14 Jan 2020, 18:57 Try... Open and Close the driver node
Capture.PNG
Code: Select all
var firstsel = Node.FirstSelected();
if ((firstsel == "") || !Node.ConExists(firstsel, 'Matrix') || !Node.ConExists(firstsel,"Selection"))
{
params.SetTerminationFlag();
return;
}In the UU10, the R shortcut is being used for the Rectangle Zoomnew "R" to reset
When the tool is active R does not run the rectangle zoom so there is no conflict unless you want to rect zoom while normal moving so,trueBlue wrote: 17 Feb 2025, 16:18 Normal Move ToolIn the UU10, the R shortcut is being used for the Rectangle Zoomnew "R" to reset
So, I will be changing this to N = Reset Normal Offset
or use the current method which is Left Click = Reset Normal Offset
Which one would you prefer?
For me it does, and the Normal Move widget is still activeWhen the tool is active R does not run the rectangle zoom so there is no conflict
Cross post, so you missed my edittrueBlue wrote: 17 Feb 2025, 19:26For me it does, and the Normal Move widget is still activeWhen the tool is active R does not run the rectangle zoom so there is no conflict
So, in this case both are active
Would be best, if one widget canceled the other current widget, like the Object and Camera widgets work
Not sure if that is possible with the Normal Move widget
Are you sure this new installer is correct?clintonman wrote: 18 Feb 2025, 04:03 The last release still had the same old installer bug on one piece. Fixed now.
1.) Toolbar Manager is not used by the Normal Move Tool, there is no toolbar.trueBlue wrote: 18 Feb 2025, 18:44Are you sure this new installer is correct?clintonman wrote: 18 Feb 2025, 04:03 The last release still had the same old installer bug on one piece. Fixed now.
Have not tried it, just reading
1.) Looks like the Toolbar Manager would be a requirement for non-UU10 installation
2.) Looks like you are copying theScript and theWidget inside trueSpace, which negates Load On-Demand
The toolbar left mouse button Command and RClickCommand should be the process to load theScript and theWidget
Edit: Unless I am missing seeing this, it looks like you are not saving the CCFunctionSet.RsObj to disk
Code: Select all
function NormalMove(MouseButton)
{
if(!LoadScript("NormalMove", "NormalMove.RsObj", "Normal Move Script is not installed")) return;
if(!Node.Exists("/Widgets/Tools/Mesh editor/PE NormalMove"))
RsFileIO.LoadObject(System.GetMainDir() + "\\Scripts\\clintonobjects\\CustomScriptsStore2\\PE NormalMove.RsObj", "/Widgets/Tools/Mesh editor");
if(MouseButton == "LMB") {
Activity.Run("Scripts/CustomCommands/NormalMove/StartNormalMove")
} else {
UserInterface.OpenToolPanelViewEx2("" , "" ,"/Widgets/Tools/Mesh editor/PE NormalMove/Normal Move", 3,1,0)
}
}
, the very last step was missing. While testing I didn't want permanent changes to the CCFunctionSet. Should have copied and commented it out.Code: Select all
RsFileIO.SaveObject(mainDir + "\\Scripts\\clintonobjects\\CustomScriptsStore\\CCFunctionSet.RsObj", "/Scripts/CustomCommands/CCFunctionSet");Seems like the user pressing the toolbar Normal Move tool's LMB or RMB command would be the requirement, making the installation a true Load On-DemandScript and Widget are copied in so they can be used immediately
Ah, I see. The new load on demand is not removing the old widget from the Widgets file. I forgot the old version was not load on demand.trueBlue wrote: 19 Feb 2025, 13:25 Ran your newest installer
As said, this is not a true Load On-Demand installer because this installer loads the script and widget
Also. when you Reset to the Default Context, the PE NormalMove widget is still present
The installer does not save the Widgets without the PE NormalMove widget
HTH