Author Topic: Do I need to check "Allow Command Segment Info for Composite Commands"  (Read 1891 times)

janjan

  • Newbie
  • *
  • Posts: 42
I'm going over the manual and i got to the Options section, specifically "Allow Command Segment Info for Composite Commands".
By default this is not checked yet I do have command such as:
Set text [profileName] to '{CMDSEGMENT:1}' and this command is working.

My question, or rather 2 questions:
1. How is this still working even though i did not check the "Allow Command Segment Info for Composite Commands" option?
2. Considering CMDSEGMENT, if i have the following command:
Please;can you [enter;input] a key for [processing;evaluating]

Can I assume that this is the proper segmentation numbering:
[#0] :Please;can you
[#1] :[enter;input]
[#2] :a key for
[#3] :[processing;evaluating]

Thanks
« Last Edit: April 18, 2020, 03:56:12 AM by janjan »

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4759
  • RTFM
That option only applies to prefix/suffix commands (as mentioned in VoiceAttackHelp.pdf), so unless you intend on using those, and intend to use "{CMDSEGMENT:}" in them, that option is not required.


Yes, those would be the parts that are grouped into segments, however note that "Please" is a single phrase by itself, and not an optional part of the phrase as a whole.

If the latter is your intent, wrap it in square brackets as well, E.G. "[Please;] can you [enter;input] a key for [processing;evaluating]", which will make that segment 0, and "can you" segment 1.