Leaderboard

@Mbee: A dllstruct tutorial is here. a dll call-code generator is here. For links to usage discussion, see for exaple here.

I would choose any of these two ways to handle that. Create a multiprocess script one for the task and the other to handle the popups) or simple set a window event hook maybe using RegisterShellHookWindow or SetWinEventHook to handle the popups. Saludos

My preferred way to solve this problem would be AdLibRegister. If that doesn't work then you could have a look at OutlookEX UDF. Function _OL_Open allows to start a second script that waits for a window to pop up and then clicks it away. The second script is terminated when the main script ends.

I don't see what Adlib wont work. I use it for situations similar. Put it at the top of your script it should be running before the unexpected window comes up, and have the contents of that function be passive. Example: If WinExists() Then WinActivate() Send("{Enter}") EndIf

Wait no longer..... other member ( me ) agrees 100% with water. now you can wait for a Mod if you want

Pixel- and ImageSearch are far from being basic. Most of the people never need to use this functions as those use cases allowed by the forum rules can be coded with other functions. Look for a good real-life use case and start to code. If you have questions we will be happy to assist

maybe ? : For $i = 0 To $iItemCount - 1 Local $arg = $aHeadCode[$i] switch $arg case "1C01DB" ;"FindItem", "string to find" [, SubItem] ;Returns the item index of the string. Returns -1 if the string is not found. $ControlListViewReturn = ControlListView($handle, "", "[Class:SysListView32; INSTANCE:1]", "FindItem", $arg) If $ControlListViewReturn = -1 Then Msgbox(0,"","Not Found") Else ; If found then select : ControlListView($handle, "", "[Class:SysListView32; INSTANCE:1]", "Select", $ControlListViewReturn) ; Clic on next page place ; ... EndIf EndSwitch Next

Have a look in the first example works for you.

Please check the help file for ControlListView (already used in your script) and look for "FindItem" and "Select".

You may look at my Resources UDF (sources) where I fixed X64 compatibility many years ago. Link to my Resources UDF is in my signature ... EDIT: There is also derived ResourcesEx UDF by guinness which is compatible with latest AutoIt

Heeyo! For my current game project, I use hitboxes for collision. I have created a editor in autoit to speed up the creating process. I thought it might be good to share it with the community. The resources needed are all inside the .rar, as well as the source and the executables. The editor also requires my _Mouse_UDF, found >here, but it's also included in the .rar. Let me know what you think. Things you might want to know using this editor: "Open" will open an image file, not a text file. "New" will save a text file, not an image file. The "cursor" tool is used so you don't accidentally create a hitbox. The "sphere" tool creates a sphere hitbox from the center. The "rectangle" tool creates a rectangle from the clicked position. In the lower right corner, "MXY" means mouse xy on grid. In the lower middle, "GXY" means grid xy, it's the mouse xy on the grid according to the origin. In the lower right corner, "S: x, R: y" means there are x sphere hitboxes and y rectangle hitboxes. The green dot is your editor cursor. Screenshots 2D Hitbox Editor.rar

Hi MsgBox(0,"",cutAfter('abc 12432141 Hello-World get it', "Hell")) Func cutAfter($string, $StringCutAfter) Return StringLeft($String, StringInStr($String, $StringCutAfter) + StringLen($StringCutAfter)-1) EndFunc So long, Mega

Thanks both for your help. Sugi - It didn't seem to make any difference by adding the ' ' around the statement, but I understand what you're saying. Beerman - Adding the working directory to the end of the statement seemed to do the trick and it now runs as it should. Thanks again to you both, especially for such quick replies!