Custom script commands need to parse the modifiers manually?

Help & Support
1

My custom script command is not able to respond to the @nodeselect modifier.
You need to determine in the script if this modifier exists.

	Set Modifiers = CmdData.Func.Command.GetModifiers

	If Modifiers.Exists("@nodeselect") Then CmdData.Func.Command.deselect = False

I hope that custom scripts can automatically respond to the modifiers.

2

Haven't looked at this at all but it occurs to me that the @ symbol may not be needed here.

Just guessing...

From the Command scripting object reference manual:

"The supported modifiers are a subset of the full list of command modifiers:

admin, async, codepage, externalonly, leavedoswindowopen, nodeselect, noexpandenv, nofilenamequoting, nolocalizefiles, noprogress, norunbatch, resolvelinks, runmode"

3

I guess the two lines of code work fine, @qiuqiu simply dislikes the fact he has to use them in his script command.

4

Ah!