When creating a new profile, if one non-full command is created, paired with one full command, the profile is then saved (using "Done", as "Apply" is not available upon profile creation), and the full command is edited to become the counterpart to the other non-full command, the combined phrase will not be recognized as well as it should.
The command can be recognized when speaking the phrase with a conscious pause between both sides of the phrase (E.G. "prefix...suffix"; Only the pause appears to be important, as very quickly speaking the words themselves will still work, as long as the pause is there), but the recognition confidence will be lower than usual (E.G. ~85 vs the normal ~95).
Reloading the profile allows the phrase to be recognized even when not pausing at all between words.
E.G. (each step begins with choosing "Create New Profile" to open the "Add a Profile" window):
Creating both a prefix and a suffix works after saving
Creating a prefix, saving the profile, then creating a suffix, works
Creating a prefix, saving the profile, then creating a full command, saving the profile, then editing that full command into a suffix, works
Creating a prefix and a full command, saving the profile, then editing the full command into a suffix, does not work correctly (pause required)
Creating a prefix, a suffix, and a full command, saving the profile, then editing the full command into another suffix, works
Creating a prefix and two full commands, saving the profile, then editing one of the full commands into a suffix, works
Creating a prefix and two full commands, saving the profile, then editing both of the full commands into suffixes, works
The behavior is the same when creating the suffix first and editing the full command to become the prefix.
Tested with v1.8.3 and v1.8.3.10
EDIT: Fixed in v1.8.3.11
Topic: [v1.8.3] Full command to prefix/suffix after profile creation poor recognition (Read 1640 times)