Bug when triggering macros with Target Device if first character of name is a number

Hi all,

Running 2.6.4.9.0.3 on an Eos Ti (and replicated problem on Nomad).

I discovered a potential bug today, where if you try to specify a target device that begins with a numeric character, it either produces a syntax error when trying to specify the device, or if you do get it to take the target device command, a space is added between the number and the next character, and it will not successfully trigger.  (For example, a device called "3AM-LD-PUCK" would produce the error.)  I only tried it with the number 3.

-J

Related