Yeah, the spelling out of the numbers was the first thing I tried. Here is a screenshot of what is happening. Spoken "F ONE" gets translated to F1 and the F1 command is executed. Spoken "F TEN" gets translated to F10 BUT the F1 command is executed!
If I use a non-numeric word (I use MAP because F10 also shows the map when a menu isn't up) and "F MAP" works perfectly to invoke the F10 command.
OK.. This seems to have cleared up the F commands. F10 works now (I did also put F10 into the voice command in addition to FTEN).
Now I have another case, which might be special.
I need FOXVOX to spell out text for an entry box, in the format #TPn but I wasn't sure how the built in SPELL command would recognize # (HASH?) So I built commands to respond to the TARGET - P1 through P10. 1-9 work. Oddly again there is a digit thing going on. FoxVox recognizes "TARGET P TEN" as "TARGET P1 P10" and invokes P1. See attached:
This might be a crazy edge case that isn't worth fixing. I used
PX instead of 10 which works.
EDIT: I used JUST the numbers without the P and it works! I think I put the P in when I was having issues with the numbers. Interestingly it recognizes the spelled out numbers better than the numerals, ONE vs. 1, which seems contrary to the fix. When the P is before it, it recognizes the numerals just fine.Exception is FOUR, 4. I had to put "FOR" in to get it recognized, which again wasn't the case for the F set of commands
