On Mon, 26 Jun 2006 10:48:01 +1000, Alan Martin <[EMAIL PROTECTED]> wrote:
>Hi CM, this works: > >Command: Exec >Action: Prompt >Enter flag number... : zYes Run calculator? >Enter more commands... : >if(zYes == 1) >C:\pathto\application.exe > >> ... but when the PowerPro help took me to the Input Dialogs section, >> I got a bit lost, and I'm not sure how to go about it. > >The last thing in the Input Dialogs topic is a link to: > >*Exec Prompt flag/var text >Shows a Yes/No/Cancel dialog. Details << > >I used a var instead of a flag to receive the result from Exec Prompt. > > > > >Attention: PowerPro's Web site has moved: http://www.ppro.org >Yahoo! Groups Links > > > > > > Hi Alan, Yep, both your suggestion and Bruce's work fine, except for one minor thing. The program I'm wanting to prompt for had a button seup as such. Command: C:\Run-Backup\H Backup Normal Log.bat More Commands: *Wait for 200 "*Keys (to *windows\system32*)"a *Wait for 200 "*Keys (to *windows\system32*)"a This is because the program requires two keypresses to continue to run. Anyway, what happens now is that I click on the button. The prompt comes up, which I click yes to. The H Backup Normal Log.bat file runs. The first prompt is answered by the 'a' key. No problems so far. The next prompt is seemingly also answered by the 'a' key (as the program goes past the second prompt and starts to run - I say seemingly, because I am not actually sure, see below for description of problem). Still ok so far. Now, here is where the problem comes in - if you press a key while the program is running, it will bring up a prompt asking you if you want to abort. Somehow, using the new button setup above, (presumably) the 'a' key is sent a third time to the program, and I always get the prompt 'do you want to abort'. I have tried various combinations of wait time (400, 500, 1000), but no matter how long I tell PowerPro to wait, the program always brings up the abort message. PowerPro seems to do one of the following: 1. sends 'a' key, waits, sends 'a' key again, waits, sends 'a' key again (waiting and sending three times, despite there only being two waits+sends in the more commands box). I don't think this is likely, I think the next one more likely; 2. sends 'a' key, 'a' key somehow stays 'pressed' for slightly longer than what it is meant to, and thus is detected by the program as the second keypress (the one that starts it running - even though the second wait+send has not yet ran), waits, sends 'a' key again (for the second time which the program uses to bring up the abort prompt) I don't know which of these is happening, but if anyone can give me some guidance on tracking down what has gone wrong, that would be appreciated. -- Regards, CM ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
