Problem with a Quick Input in VA.

[iceblast]

I have been using this command for a few years. The last few months, the { was being cut off, now the first letter as well. This only happens if I'm using the command in VA to make a command. If I'm using Notepad, it works just fine.

The Quick Input delay timing is set 0.0, 0,0

It should type out.
{ACTIVEWINDOWTITLE}

Instead it's only typing.
CTIVEWINDOWTITLE}

It has for a few months been doing this.
ACTIVEWINDOWTITLE}

I've just been quickly adding the { instead of looking at the command.

Code: [Select]

Press and release Right Shift+[ { keys
Quick Input, 'ACTIVEWINDOWTITLE'
Press and release Right Shift+] } keys

Now, if I do this, the command works again.....

Code: [Select]

Pause 0.1 seconds
Press and release Right Shift+[ { keys
Quick Input, 'ACTIVEWINDOWTITLE'
Press and release Right Shift+] } keys

Over the years I've seen commands do this, where it's like the command moves too fast, and seems to skip the first line of a command, and adding a pause in the first line for the command seems to fix it.

[Pfeil]

Unfortunately that is currently a known issue with the new GUI in the beta version.

[iceblast]

👍

[Gary]

@iceblast - which input/action are you trying this out on?

[iceblast]

It's a Voice command.

Usually when making a Begin a Condition command, but I'm pretty sure it has this issue if I try it anywhere within VA it's self. It works fine anywhere else, like notepad.

Just tested it again, and the issue is as said above, and works outside of VA.

Adding a 0.1 second delay does fix the problem, but I have experienced this issue for a few years, where the first line of a command seems to be ignored, but a small pause seems to fix it. It's like VA starts to process the command a hair faster than it's ready for, yet, for some reason, it does see the pause, and it's on the first line of the command. Strange.....