Show and Hide Commands

[clintonman]

For the same reason you moved the Scripts/Commands/visibility scripts into the Visibility Function Set
And more importantly, I am still seeing the bogus commands in the Command History
Example:
Open the Command History
Run a jScript with no code and with nothing selected
For me, this entry is being shown:
ScriptObject.RunCmd("script object package/delete")
Note: The entries may or may not show or it may be a different entry
I suspect it will be one of the last Scripts/Commands used previously

I was not planning on removing the tS original xml files, except the modified OnNewScene

I moved the Scripts/Commands/visibility scripts into the Visibility Function Set so they could share code. So you are saying you want to make a new function set inside UUCommands to share code? I don't remember there being that much overlap in the Scripts/Commands.

I'll try your example when I can get to the computer.

Yes, or just add jScripts inside UUCommands
Move Scripts Commands to UUCommands.png

I'm ok with either one. I just don't want a single function set with a thousand lines of code. If you make a function set and it gets too long, break it up into smaller function sets.

[trueBlue]

My current UUCommands

[trueBlue]

IsolateSelected

Code: Select all

cmd='visFnSet = Node.AccessFnSet("/Scripts/UUCommands/Visibility Function Set");VisuFS = Node.AccessFnSet("/Scripts/UUCommands/VisUtility Function Set");visFnSet.VisuFS = VisuFS;visFnSet.IsolateSelected();';RsApp.RunScriptBuffer(cmd);

Can you stop the above from running if nothing is selected and if the selected object does not have a Matrix?
Currently, it hides everything with nothing selected

[clintonman]

The Visibility Function Set is using:
Activity.Run("/Scripts/UUCommands/CloseORASettings");
Can this be incorporated into another Function, and remove the CloseORASettings script?
...

Does this do anything? I did some tests with and without CloseORASettings and didn't see any difference.

IsolateSelected

Code: Select all

cmd='visFnSet = Node.AccessFnSet("/Scripts/UUCommands/Visibility Function Set");VisuFS = Node.AccessFnSet("/Scripts/UUCommands/VisUtility Function Set");visFnSet.VisuFS = VisuFS;visFnSet.IsolateSelected();';RsApp.RunScriptBuffer(cmd);

Can you stop the above from running if nothing is selected and if the selected object does not have a Matrix?
Currently, it hides everything with nothing selected

It is done. Also checks for no selection.

[trueBlue]

The Visibility Function Set is using:
Activity.Run("/Scripts/UUCommands/CloseORASettings");
Can this be incorporated into another Function, and remove the CloseORASettings script?
...

Does this do anything? I did some tests with and without CloseORASettings and didn't see any difference.

IsolateSelected

Code: Select all

cmd='visFnSet = Node.AccessFnSet("/Scripts/UUCommands/Visibility Function Set");VisuFS = Node.AccessFnSet("/Scripts/UUCommands/VisUtility Function Set");visFnSet.VisuFS = VisuFS;visFnSet.IsolateSelected();';RsApp.RunScriptBuffer(cmd);

Can you stop the above from running if nothing is selected and if the selected object does not have a Matrix?
Currently, it hides everything with nothing selected

It is done. Also checks for no selection.

It closes all of the ORA panels in the Stack/Settings when you run the original Show Object Attribs command

[clintonman]

The Visibility Function Set is using:
Activity.Run("/Scripts/UUCommands/CloseORASettings");
Can this be incorporated into another Function, and remove the CloseORASettings script?
...

Does this do anything? I did some tests with and without CloseORASettings and didn't see any difference.

IsolateSelected

Code: Select all

cmd='visFnSet = Node.AccessFnSet("/Scripts/UUCommands/Visibility Function Set");VisuFS = Node.AccessFnSet("/Scripts/UUCommands/VisUtility Function Set");visFnSet.VisuFS = VisuFS;visFnSet.IsolateSelected();';RsApp.RunScriptBuffer(cmd);

Can you stop the above from running if nothing is selected and if the selected object does not have a Matrix?
Currently, it hides everything with nothing selected

It is done. Also checks for no selection.

It closes all of the ORA panels in the Stack/Settings when you run the original Show Object Attribs command

I think you deleted the wrong post. The one where you mentioned objects with no ORA was helpful. Now I can test the change.

[trueBlue]

Sorry, having internet issues and this Forum's Web Server errors

[clintonman]

Here is the visibility fs with the isolate selected fix.
Testing shows that CloseORASettings doesn't work if you move it into the function set, it has to remain it's own thing.

[trueBlue]

Thank you, that is what I suspected

Trying to better organize scripts being used in the UU
I have committed using your UUCommands/FN Sets and Scripts
Would be nice if everything is in one place, not necessarily your CustomCommands scripts

Currently, the Delete LMB command uses:
var GlobalFS = Node.AccessFnSet("Scripts/CustomCommands/Global Function Set");
Can the Global Function Set be recreated in UUCommands, so that it is in one place?
If so, can you add a Function for Copy?

Also, it looks like you have improved 3D & 2D Grouping and Ungrouping for your Scene View 2
Can you add a FN Set 'Encapsulation' to the UUCommands?
Scripts/Commands/
Unglue 'Bad name' Should have been '3DUnencapsulate'
2DEncapsulate
3DEncapsulate
Unencapsulate 'Bad name' Should have been '2DUnencapsulate'

[clintonman]

Thank you, that is what I suspected

Trying to better organize scripts being used in the UU
I have committed using your UUCommands/FN Sets and Scripts
Would be nice if everything is in one place, not necessarily your CustomCommands scripts

Currently, the Delete LMB command uses:
var GlobalFS = Node.AccessFnSet("Scripts/CustomCommands/Global Function Set");
Can the Global Function Set be recreated in UUCommands, so that it is in one place?
If so, can you add a Function for Copy?

Also, it looks like you have improved 3D & 2D Grouping and Ungrouping for your Scene View 2
Can you add a FN Set 'Encapsulation' to the UUCommands?
Scripts/Commands/
Unglue 'Bad name' Should have been '3DUnencapsulate'
2DEncapsulate
3DEncapsulate
Unencapsulate 'Bad name' Should have been '2DUnencapsulate'

Moving Global FS to UUCommands can be done, but not automatically. Buttons can be altered. Scripts would have to be manual. I'll check the exports to see how big a job it is.

The new Scene View grouping/ungrouping is not the same as encapsulate/unencapsulate.
It adds and removes objects from groups using same as this link:
file:///C:/xampp2019/htdocs/clintons3d/plugins/truespace/utility/heirarchy.html

Did a search and global fs only being used in maybe 15 scripts, that's doable.