junkew Posted February 19, 2016 Share Posted February 19, 2016 Example() Func Example() ; Run Notepad with the window maximized. Local $iPID = Run("notepad.exe", "", @SW_SHOWMAXIMIZED) ; Wait 10 seconds for the Notepad window to appear. WinWait("[CLASS:Notepad]", "", 10) ; Wait for 2 seconds. Sleep(2000) ; Close the Notepad process using the PID returned by Run. ProcessClose($iPID) EndFunc ;==>Example In above example I do not fully understand why the WinWait is there whereas the $iPID already has a running program. At what point is Run continuing with the next line in the script. Is there a timelap moment between having a process ID and having a window? FAQ 31 How to click some elements, FAQ 40 Test automation with AutoIt, Multithreading CLR .NET Powershell CMDLets Link to comment Share on other sites More sharing options...
water Posted February 19, 2016 Share Posted February 19, 2016 Run returns as soon as the program has been started. Then notepad starts processing and sooner or later displays the window. So yes, I think there is a timelapse between Run returning the PID and Notepad displaying the window. My UDFs and Tutorials: Spoiler UDFs:Active Directory (NEW 2022-02-19 - Version 1.6.1.0) - Download - General Help & Support - Example Scripts - WikiExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example ScriptsOutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - WikiOutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - DownloadOutlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - WikiPowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - WikiTask Scheduler (NEW 2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki Standard UDFs:Excel - Example Scripts - WikiWord - Wiki Tutorials:ADO - WikiWebDriver - Wiki Link to comment Share on other sites More sharing options...
junkew Posted February 19, 2016 Author Share Posted February 19, 2016 thx. But does this then make sense? Run returns PID according to help but when should I then wait with a processwait $result = Run(..., $workingDir, $windowState) $PID = ProcessWait($processName, 60) or $PID = Run(..., $workingDir, $windowState) FAQ 31 How to click some elements, FAQ 40 Test automation with AutoIt, Multithreading CLR .NET Powershell CMDLets Link to comment Share on other sites More sharing options...
water Posted February 19, 2016 Share Posted February 19, 2016 ProcessWait does not make sense as $PID is the same as $result. But WinWait makes sense because the PID is returned before the WIndows gets displayed. My UDFs and Tutorials: Spoiler UDFs:Active Directory (NEW 2022-02-19 - Version 1.6.1.0) - Download - General Help & Support - Example Scripts - WikiExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example ScriptsOutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - WikiOutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - DownloadOutlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - WikiPowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - WikiTask Scheduler (NEW 2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki Standard UDFs:Excel - Example Scripts - WikiWord - Wiki Tutorials:ADO - WikiWebDriver - Wiki Link to comment Share on other sites More sharing options...
BrewManNH Posted February 19, 2016 Share Posted February 19, 2016 (edited) The WinWait in the example serves no purpose, I'm not even sure what why it's in there because it doesn't do anything in the script. It's pointless to have it. Edited February 20, 2016 by BrewManNH typo If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag GudeHow to ask questions the smart way! I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from. Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays. - ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script. - Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label. - _FileGetProperty - Retrieve the properties of a file - SciTE Toolbar - A toolbar demo for use with the SciTE editor - GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI. - Latin Square password generator Link to comment Share on other sites More sharing options...
junkew Posted February 20, 2016 Author Share Posted February 20, 2016 winwait makes sense processwait seems only to be usefull when you are not starting the application yourself Although I have run below script it seems not to close the wordpad process whereas for notepad things go fine Example("write.exe","[CLASS:WordPadClass]") Example("notepad.exe","[CLASS:Notepad]") Func Example($p,$w) ; Run Notepad with the window maximized. Local $iPID = Run($p, "") ;~ consolewrite("PID after RUN " & $iPID & @CRLF) $i=0 while not processexists($p) and $i <=500 $i=$i+1 consolewrite("Process waiting " & $p & $i & @CRLF) ;~ sleep(1) WEnd ;~ $iPID = ProcessWait($p, 60) $i=0 while not winexists($w) and $i<=500 $i=$i+1 consolewrite("Window waiting " & $w & $i & @CRLF) ;~ sleep(1) WEnd ; Wait for 2 seconds. Sleep(2000) ; Close the process using the PID returned by Run. ProcessClose($iPID) ; Wait for 2 seconds. Sleep(2000) EndFunc ;==>Example FAQ 31 How to click some elements, FAQ 40 Test automation with AutoIt, Multithreading CLR .NET Powershell CMDLets Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now