Version 3 has been released!

{TS} command

Define a set of triggers that a RemoteSign can use to trigger scripts 


{TS} slot ␑ style  statusvar ␑ label width forecolor backcolor ␑ nButtons  triggers

  • slot - an integer defining the desired order of presentation in a user interface 
  • style - variable style as follows:
    • 0: delete any existing trigger set for this slot number
    • 1: On/off
    • 2: Percentage
    • 3: Number
    • 4: Enumerated radio buttons
    • 5: Single action push buttons(s)
    • 6: Text
    • 7: Color
  • statusvar - the variable used to indicate a status of the trigger set, zero means none
  • label - text to use in the user interface
  • forecolor - foreground color of the label
  • backcolor - background color of the label
  • nButtons - number of trigger buttons defined
  • triggers - an optional list of trigger data to define display of options and return data, separated by DC1 characters. Each trigger has these parts:
    • scriptindex - index number of the script to run
    • parameters - a list of parameters that will overwrite parameters in the script, separated by pipe characters |. An empty parameter will not overwrite the script parameter.
    • image - an image name to use in the interface
    • text - text to use for the trigger button (on top of image)
    • tforecolor - foreground color of the trigger text
    • tbackcolor - background color of the button and 
Note #1: Trigger data is not required for styles: Percentage, Number, Text, Color

If a non-zero variable number is defined, the RemoteSign handling the {TS} command is expected to send a {SETVAR} command with the value triggered by the user. If a script is defined that is expected to be sent via a {RUNSCRIPT} command, after any {SETVAR}

Overview and list of all RemoteSign commands: API reference

Supported by:
RemoteSign Sequencer 3.7
RemoteSign ScriptRunner 1.0

See the overview of RemoteSign scripting