JoeCool

Interesting I 'll look at it

Hello, On one side I have few Autoit automation scripts already working perfectly and on the other side I have few python lib already working 🐵 Of course I can load autoitX.dll and call some functions or I can use this python autoitX wrapper from pypi : https://github.com/jacexh/pyautoit It works fine for my quick tests. But my autoit scripts need some functions from UserDefinedFunc, especially GuiListView Is someone know is someone here has made a implementation for UDF (GuiListView) ? Thanks

I really enjoy this debugger I just stump on 2 bugs, on v0.47 can we still report them here ? This one is probably already know and not really a bug but, because the files are put in the debug folder, @scriptdir report that folder, so if you have some files to open don't forget to copy them manually into the Debug folder. The other one made me smile ... here a pic of the error... Ok I have a big array [20][7][10][2] with a big Initialization string .... Language check is fine and its works fine when I run the script. But poor debugger... it said, whatthehell is that string, I'm out of here

Arrghh ! I didn't see that option before .... It woks when you cancel Windoze behavior... Thanks !

Ok ? 40 views and nobody ever see that or thing it is a bug ??? lol

I'm pretty sure all autoit gurus here will have an answer for me :-) so here the code : #include <guiconstants.au3> #include <constants.au3> func wndMinimize() guiSetState( @SW_MINIMIZE, $gui ) endfunc func wndMaximize() guiSetState( @SW_MAXIMIZE, $gui ) endfunc func wndRestore() guiSetState( @SW_RESTORE, $gui ) endfunc func wndClose() exit endfunc opt( "GUIOnEventMode", 1) $flag = bitOr( $WS_SYSMENU, $WS_MINIMIZEBOX, $WS_SIZEBOX, $WS_OVERLAPPEDWINDOW, $WS_CLIPSIBLINGS) ;$flag = 0 $gui = guiCreate( "Hello World", 200, 200, 200, 200, $flag ) guiSetOnEvent( $GUI_EVENT_MINIMIZE, "wndMinimize" ) guiSetOnEvent( $GUI_EVENT_MAXIMIZE, "wndMaximize" ) guiSetOnEvent( $GUI_EVENT_RESTORE, "wndRestore" ) guiSetOnEvent( $GUI_EVENT_CLOSE, "wndClose" ) guiSetState( @SW_SHOW ) while 1 sleep( 1000 ) wend I basicly just redefine Minize, Maximize, Restore and Close ... because in my application I will need to do some stuff in there .... but here the problem, script start and display a hello world, if I minimize it, and click on the icon on the task bar( actually restoring it ) the restore works fine, window is at the right place... but if I maximine the window and minimize it , the restore bring back a window NOT maximized ! if you comment out this line guiSetOnEvent( $GUI_EVENT_RESTORE, "wndRestore" ) and let windoze do the restore a maximized window minimized in the task bar will be restore as a maximized window, so do you think ? ... maybe there is a "bug" in the "guiSetState( @SW_RESTORE, $gui )" ... :-)

Thanks I did delete my post!

duh ! and it is my exact first message, why not extend a bit the language to have optional byreference paramaters in function definition .?????...

ok then, so base on your comments could you suggest to remove completly byreference parameter, 'cause there is not gain to have it lol it will lead to a less complicated language to maintain !!! but ... i'm still thinking, we should have optional byreference paramaters in function definition ....

Currently passing optional parameters is by value ... so copying alot of arrays is not fun sometime... I will love to have something like this (optional byref parameter ) With the current syntax ...(the last parameter could be byref and optional) func blah( $x, byref $a, byref $b = 0) ... endfunc Passing no value is not more difficult than before, I guess ... Passing something byref is just passing a pointer(of some sort on the stack).... (we need to deal with initiazation to something not 0) Better solution will be to have a opt specifier ... func blah( $x, byref $a, opt byref $b , opt $c = 22 ) ... endfunc because initializing byref var (a pointer) to something can be dangerous ... func blah( $x, byref $a, byref $b = 0x1231) ;not good endfunc what do you thing .... it can be pretty useful I think

yes , of course maybe usuful when i will code some read/write byte port (com, lpt, usb ... ) drivers in autoit ... something like ... $arr[1024] stuff with all strings and all protocol bytes (0x00 to 0xFF ) stringToBinary(stringFromASCIIArray($arr)) to have a byte buffer ... i should stop drinking beer now and go to sleep !

oh i see i found it.... binary( ) has nothing to do with hex number neither binary NUMBER (b10010100) ... it can take 2 forms of string not interpreted the same way... binary("abc") = binary("0x616263") $str = binary("hello world") is the same has $str = stringToBinary("hello world") who will just encode caracters to ascii byte default encoding value ... and binary("0x616263") is a raw encoding form ... EDIT i changed this message a few time... i was exploring the help file

why 0x00270FF6 != 2559990 ? unsigned hex positive int32 can someone explain me that please if binary("0x00270FF6") = 2559990 then msgbox(0, "True", "" ) else msgbox(0, "False", "" ) endif

lol ur right ... I didn't think hard enough I don't use the _array package, i have since long time my own few packages who do all that stuff (array, matrix etc), i was just writing a script for someone and wrote those 2 functions on the fly for him ... i should always think before coding

bump ! so nobody find this should be in Array UDF ? it is already in my udf anyway