Leaderboard

Interesting thread, somehow missed it before. For what it's worth, speaking from personal experience, I think it's worth pursuing (regardless of the merits of having a native AutoInux), because nothing ever taught me more about programming design and coherent, consistent language structure than when I had to develop my own programming environment a few years back (now mainly used by other people). If you can spare the time and effort and you think it's worthwhile, make it happen.

roselpi, Having now read back a bit more in the thread, I feel I must comment on this phrase from your last post: I am afraid that I do not agree with you here. You cannot expect AutoIt to provide functions that do exactly as you expect/wish in every case - it gives you a good set of basic commands which allow you to do practically anything with a bit of imagination and hard work. The UDFs we include with the standard AutoIt install are a good example of that - as the main author of the current _ArrayDisplay code I can assure you that its present behaviour is the result of many requests for an auto-expanding dialog, rather then the old fixed size one that used to be offered. My personal ExtMsgBox UDF that I suggested to you above is another case where basic AutoIt commands are combined to give you something much more polished than the basic Windows dialog. So what you are actually asking is for someone else to do all the hard work so that you can write a simple one-line command in your script which produces exactly what you require. Well, if that is not lazy - then I do not know what is! However, you finish with this line: And this is exactly what I would recommend. Take the existing _ArrayDisplay code (you actually need to look at ArrayDisplayInternals.au3) and try to understand what is going on within it - the code is actually pretty well commented for a standard UDF which will help enormously. You should then be able to write your version, omitting or changing various sections to get precisely what you want. I am certain people here will offer help on any questions you might have - as long as you have done due diligence with the Help file and forum search facility beforehand. That is the best way to learn AutoIt - getting down and dirty with the code. M23

It starts at 201, just add 1 for each icon (like 2nd is 202, 3rd is 203, etc...)

You can always use RegRead and RegWrite instead of exporting to a reg file.

OnEvent functions can not have parameters, so none of your $length# parameters can be used in the function. Also, you have declared the $length# variables in the global scope but you reused the same names in the parameters for the genpassword function. So, because the parameter variables are ignored, the global variables are being used instead, and they don't contain any values. You can call the function without using OnEvent with values in the parameters, and those will be used, but you don't do that.

Your imagesearch needs to be inside the loop, it only checks it once before going into the loop as written.

If you want to use ressources included in the .exe, I would strongly recommend that you use RessourceEX UDF, unless you want to reinvent the wheel. The example provided show you how to add different resources. But if you only need icon to a button, you can do it like this : #AutoIt3Wrapper_Res_Icon_Add=%AUTOITDIR%\Examples\Helpfile\Extras\Soccer.ico #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <ButtonConstants.au3> Local Const $iHeight = 450, $iWidth = 470 $g_hGUI = GUICreate('Resources Example', $iWidth, $iHeight, Default, Default, BitOR($GUI_SS_DEFAULT_GUI, $WS_MAXIMIZEBOX, $WS_SIZEBOX)) Local $iBall = GUICtrlCreateButton('Click', $iWidth - 168, 72, 68, 71, $BS_ICON) GUICtrlSetImage($iBall, @AutoItExe, '201') ; Icon resources added with #AutoIt3Wrapper_Res_Icon_Add, can be directly used without the UDF. Global $picIcon = GUICtrlCreateIcon(@AutoItExe,201,100,10,32,32) GUISetState(@SW_SHOW, $g_hGUI) While True Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop EndSwitch WEnd You will need to compile the script first...