Nuance Management Center

Administrating Dragon with the Nuance Management Console
CmdSet3: <> <>
In this case, all of the two-list-only commands would look exactly the same and there is no
other context to differentiate them, other than comparing the list values.
We do not want to consider all commands with this pattern to be in-conflict, so a direct
comparison with the list names is performed.
Example 3:
Commands with different list names are not considered to be in conflict as long as the
remaining spoken form of the command does not match another command in a previously
loaded command set or in MyCommands ( have the same ‘signature’). However, the resulting
commands in the vocabulary could conflict at the list-value-level with unpredictable results.
So in the above case, the commands are treated as follows:
CmdSet1: <list5> <list6> // Loaded first. No Conflict.
CmdSet2: <list7> <list8> // Differs from CmdSet1, so no conflict.
CmdSet3: <list5> <list6> // Conflicts with command from CmdSet1
The command in CmdSet3 conflicts with the previously loaded command from CmdSet1, so
there is a conflict and the command is treated as Not Active.
Conflict checking sequence for Command Sets
The following is the typical conflict checking sequence performed for Command Set
commands:
1. As each Command Set is loaded (in alphabetical order), the commands and lists in the cur-
rently loading Command Set are compared against previously loaded commands and lists.
2. Commands with the same name and availability (Global, Application, Window) conflict as
will commands that use a list with the same name as a list that is from a different, previously
loaded, Command Set.
3. If a conflict is detected, the commands that are in-conflict are marked as ‘not active’ and are
not loaded into the vocabulary. The first command loaded with the same name/availability
is the ‘active’ one.
4. Once all of the Command Set commands are loaded into the ‘Master Command Set’, the
entire collection of commands is then compared to any custom commands that are defined
in MyCommands (MyCmds.dat). If there is a conflict, the command in MyCommands is
treated as the active command.
Custom commands in MyCommands override any conflicting commands and lists from the
command sets.
Conflict Detection during a Session
If changes are made to custom commands (MyCommands) during a user session, the
commands in the ‘Master Command Set’ collection are reevaluated to determine if the active
state of any of the commands should change.
If a new command conflicts with commands in the Command Sets, then those Command Set
commands become inactive.
135