{Wait999} breaks keys to send

[thegene]

I'm having trouble with the Keys to send feature. I experimented, and I am able to send normal keys to notepad, but if I enter a {Wait###}, nothing will happen after the wait command. I did a {typingdelay500} and it only printed one character from the string after the command. The $ command works. I've attached a .p2r that I have been using to try to figure this out.

Also, I tried downloading and using some example .p2r files to see if maybe I could get someone else's {Wait999} command to work, but when trying to load them it fails. I get a ElevateAtStartup error... The system cannot find the System.Diagnostics.Process.StartWithShellExecuteEx... ? I dunno.

[RobLatour]

Its working fine on my computer.

A few of notes:

first the 'listen for' in the card that you have attached is
type what i say
but should likely be
type what i say $

WIth the $ include the command you would give your google device would be
ok google tell my computer to type what I say this is a test
and that would work because the 'this is a test' part is allowed with the use of the $ in your Listen for field

However, with the $ not included in your Listen for field, as in the card you have attached, you could only say
ok google tell my computer to type what I say
for a match to occur.

If you said
ok google tell my computer to type what I say this is a test
there would be no match because your Push2run card is looking for (exactly)
type what I say
and it got
type what I say this is a test

Additionally, the Keys to send field in the card you have attached is
type what I say {Wait999} and then there is this
but should likely be
type what I say {Wait999} and then there is this $

I hope this helps explain things.

Rob

[thegene]

I removed the $ to eliminate variables from the test. The card doesn't work with the {Wait999} regardless of how I run the card. Like, even if I do it through the mouse. So, I don't think it's that I'm saying the wake command wrong because of the missing $.

[RobLatour]

Can you please post the contents of your Pusb2Run session log?

[thegene]

I turned my computer off last night, so it seems to be pretty empty. I re-ran the "type what I say" card through right click -> Run and got the same result, where nothing prints after the {Wait999}. Here's the Log.

2019-11-23 10:01:01.764 - Push2Run version 2.4.0.0 started

2019-11-23 10:01:01.768 - Windows UAC notify feature is on

2019-11-23 10:01:01.769 - Administrative privileges are enabled

2019-11-23 10:01:01.825 - Current network adapter is Local Area Connection

2019-11-23 10:01:01.844 - Network status is up

2019-11-23 10:01:05.625 - Connection with Pushbullet established

2019-11-23 10:01:05.919 - Request to Pushbullet to keep account active (ok)

2019-11-23 10:08:46.028 - Client requested to run the currently selected entry, description is notepad
2019-11-23 10:08:48.583 - action completed

[RobLatour]

well that looks fine. What version of Windows are you using?

[thegene]

Yeah, it doesn't really make sense.

Windows 10 Pro version 1909. Build 18363.476.

[RobLatour]

That's what I am using too, and it works for me?

Are you running the program with administrative privileges, if yes, can you please try turning them off?

[thegene]

Ah, yeah, it worked when I turned off Admin privileges. I notice Admin privileges does some odd things. I wasn't able to drag and drop to create new cards with Admin on either.

[RobLatour]

ok - thanks - that explains it.

Sorry for not thinking of that earlier, but if Push2Run is itself running with administrative privileges it will not be able to reliably send keystrokes to a program unless that program is running with administrative privileges too (its a Windows thing). There is actually a note in the help about that, but its way down and easy to miss.

To correct for this, if you are going to be running Push2Run with administrative privileges then you also need to check the option 'Admin privileges' on your Push2Run card - and then it should work.