Leaderboard

Local $b = Binary("") initializes the variable to a binary type and not to a string and that's the reason why it works. Br, UEZ

Basically, AdlibRegister() registers a function to be called every X miliseconds. You create the button as disabled and then tell the function to enable the button to run once every 5 seconds. After it's first run, the "Run every 5 seconds" command is disabled, so the button is disabled, waits 5 seconds, and re-enabled. Your code works even though the unregister command is not there because every 5 seconds, it's still setting the button to be enabled. If you were to put code to try to disable the button again, 5 seconds later (or less depending on the period of time that has passed) it would be re-enabled. again because the code is constantly being executed.

GUICtrlSetState($Login, $GUI_DISABLE) and then AdlibRegister("", 5000). When you want to start the 5 seconds of disable. Create Func that has GUICtrlSetState($Login, $GUI_ENABLE) then AdlibUnRegister

I think without using GDI/GDI+ it is not possible to modify the taken screenshot. I cannot remember whether this version already supports multi monitors but you can give a try -> Otherwise AutoIt Windows Screenshooter supports multiple monitors. Br, UEZ

Infragistics seems to be having full support for ui automation and as such you should be able to get to the grid interfaces to get the details unfortunately I do not have a demo application available to check / enhance the AU3 ui automation UDF but see these links http://help.infragistics.com/Help/Doc/WPF/2012.1/CLR4.0/html/Developers_Guide_UI_Automation_Support.html http://www.infragistics.com/help/windows-forms/Coded_UI_Test_Extension_Overview.html http://www.infragistics.com/help/windows-forms/Using_the_Coded_UI_Test_Extension.html

You should verify with UISpy.exe or Inspect.exe that you can get the information you need. In the gray bar just above this text you see the post or reply number (#17) to the right (my name is at the left side). In the UI Automation example by junkew then find post/reply #71. Probably at page 4.

Beli, You can only FileInstall individual files into an existing folder, so I would first create a suitable tree within the "temp" folder with DirCreate before Fileinstalling each of the files that you wish copy into the relevant folders. A bit more code for you to write, but this approach has worked for me in the past. M23.

hello and welcome to AutoIt and the forum, this is how i did it: using 7zip (freeware and open source) i distribute a group of auxiliary files with my script. in the script folder, i put files 7z.exe & 7z.dll i put all auxiliary files in a subfolder named AuxFiles before compile, i create a 7zip archive, like this: (DOS command) 7z.exe a AuxFiles.7z AuxFiles* and this is the part of the script: ; declare variables Global $sTempPath=@TempDir&'\MyScript_files\' Global $sTempPath_program=$sTempPath&'program\' ; embed/extract the 7zip program files and the archive to be extracted DirCreate($sTempPath) FileInstall('AuxFiles.7z',$sTempPath,1) FileInstall('7z.exe',$sTempPath,1) FileInstall('7z.dll',$sTempPath,1) ; extract the archive DirCreate($sTempPath_program) RunWait($sTempPath&'7z.exe x AuxFiles.7z -o"'&$sTempPath_program&'" -aoa',$sTempPath,@SW_HIDE) for better performance you can eliminate the 7z.exe and use the 7z.dll directly, use the 7zip UDF here: '?do=embed' frameborder='0' data-embedContent>> also there is a pure AutoIt archiving instead of 7zip, here: '?do=embed' frameborder='0' data-embedContent>> try it out, let us know if you need further guidance.

codeninja, Download the UDFs here and download and run the code in the "Simple spy demo" code box in the middle of the first post. Then click the Grid control (to set focus) and press Ctrl+w. You'll see info in the edit box. To print all controls (including non-visible) in Scite console run the code in post 71. You can also run the UISpy.exe (old) or Inspect.exe (new) tools from Microsoft. If you can get information with these tools you know that the controls can be handled with the Microsoft UI Automation framework.

Have you tried using the Ping command from AutoIt?

To automate these Infragistics controls you need the Microsoft UI Automation framework. You find an AutoIt implementation in this example. From the Infragistics website here (search for "ui automation"): "The Infragistics WPF suite of controls fully support Microsoft UI Automation. ... Another key use of UI Automation is automated testing; the framework allows test scripts to access and interact with the UI elements."

I've always thought of "Local" to mean "Local to the current scope". It's just that outside of a function that the current scope happens to be the global scope. That's pretty much how scope is differentiated within the internals so it's an OK way to think about it.  Allowing the feature to create a new global variable from within a function was probably a mistake (no matter how sometimes useful - i.e. We should have just left it as Dim with no Local and Global).

What is chat for if not hair splitting? I concede that magic numbers are inferior in all cases, but only for the typo argument. Being able to error the compile for a typo is killer. However, I am lazy as balls and will no doubt continue to use the most familiar numbers.