Having difficulty making commands

[Clayton Hann]

I'm using this to help write notes.  I have some templates I'f like to use shortcuts for:

For example. I'd like to say "insert physical trigger"

and have it produce:

TTP at A-1 pulley of
+ nodule palpated at A-1 pulley of
+ triggering noted on exam

I almost had it working by adding some of the commands to "basic".   I added something like:

- name: "insert physical trigger"
    description: >-
      Types "trigger finger physical".
    biasFactor: 1.2
    functions:
      - name: "type"
        fixedArguments:
          - " TTP at A-1 pulley of\n+ nodule palpated at A-1 pulley of\n+ triggering noted on exam "

Unfortunately the windows health record program  has what looks to be a early spinoff version of notepad in which we enter the data.  It did not respect the /n and made it all one line. 

If you say "enter" it definitely does a carriage return, though, which probably can get it done. 

Any idea how I could get that function to work?  I guess the best way would be to

combine typing with a carriage return command between them.  Any ideas how to do this?

[Utterly Voice]

Hello Clayton,

It sounds like the application you're typing in is processing \n in an unusual way. I tried your command in Notepad, and it works as expected. I think you are correct; the best way to type multiline content in your application is to use explicit enter key presses. Give this a try:

  - name: "insert physical trigger"
    description: >-
      Types "trigger finger physical".
    biasFactor: 1.2
    functions:
      - name: "type"
        fixedArguments:
          - " TTP at A-1 pulley of"

      - name: "keyPress"
        fixedArguments:
          - "enter"
      - name: "type"
        fixedArguments:
          - "+ nodule palpated at A-1 pulley of"
      - name: "keyPress"
        fixedArguments:
          - "enter"
      - name: "type"
        fixedArguments:
          - "+ triggering noted on exam "

Also, you may want to consider adding commands like this to a new mode file. This way you do not complicate the basic mode, which is almost always active.

--
You received this message because you are subscribed to the Google Groups "utterlyvoiceusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to utterlyvoiceus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/utterlyvoiceusers/53b7447d-b75c-4ad4-abd4-4b4e18ba936bn%40googlegroups.com.

[Utterly Voice]

Alternatively, try using "\r\n" instead of "\n" in your original command. Most modern Windows applications acknowledge "\n" as a newline, but some older programs may require a full carriage return.

[Utterly Voice]

Actually, we did some further testing on this, and we are seeing some inconsistent behavior with "\n" in the "type" function in various applications. This is something we can improve in the next version of Utterly Voice. In the meantime, try one of the workarounds above.

[Clayton Hann]

The workaround worked.  Thanks for your help in this.

[Utterly Voice]

Update: the latest version (1.07) has fixed the issue with "\n" in the type function. It should work fine now in all applications.

To view this discussion on the web visit https://groups.google.com/d/msgid/utterlyvoiceusers/8d151d07-297c-456d-a8f6-d5dea2d7f036n%40googlegroups.com.