hgeras

Well although i cant really get the difference from the description of help file i dub me the complete idiot Thx for the fast responses both.

Well it has been some time since i used autoit. Im running the latest official release (not BETA) and windows Vista. I run this simple test code : #include <INet.au3> $temp = _INetGetSource('www.autoitscript.com') $array = StringRegExp($temp,'href(.*?)>',1) MsgBox(0,"",ubound($array)) Well if you check the source code yourself you will see that this pattern exists quite many times in there. But the result i get is always 1 which means it stops on first occurence. I have also tried '(?i)href(.*?)(?i)>' at search pattern but no luck. First time with this command but either something is wrong or im completely idiot. PS i have executed the example code of StringRegExp and the result is the same . Although ubound should show 3 it is 1 again. Any ideas?

I think it must be about 6 months ago when i first posted my tool NvTempLogger here in these forums . Although no particular success , right now it is used by a few thousands of people. It is now an official tool of Guru3d.com and i'm proud of it! I'd like to say thanks to the whole team cos if it wasn't for AutoIt then none of this would have happened. It shows that it is quite powerful and can easily compete to other more popular languages... Of course it isn't the first time i say this... But, it has limits of course. The favour: There are lots of mails asking me to implement a D3d OSD support so they can watch (much like FRAPS) temperature while running D3D applications. I can but only swim in the swallow waters of C++. I tried to figure out myself but it is too much info messing with Direct X SDK. I want to make a dll to call through Autoit and giving it simple text to project on screen. I know that most of you here are quite familiarized with C++ . So , can you help me with this? Direct me somehow? Or if you have some alternative solutions. Thanx even for your time reading this.

You must be sure that if i had something helpful i would say it... I just wanted to tease you.... But i have seen in some sites that before the address they use something like "username:password"... I dont know if that is only for standard windows login or it could be used in every web page.... Just give it a try , though.... C ya

Your link is down so i cant have a look at your code ... Although from what i read a look wouldnt be enough... I suspect that you either use a continuously growing array (_ArrayAdd maybe) or creating new variables until AutoIt reaches its limits....

Why dont you ask the author of the InetGetSource UDF? I just couldnt hold it....

Although AutoIt documentation is clear as crystal,i'll tell you a hint... A 17" monitor has a diagonal of 17x2.54 = 43.18cm... The aspect ratio is 4:3 , right? So according to Pythagoras : (43.18)^2 = (4x)^2 + (3x)^2 => 1861.54 = 25x^2 => x^2 = 1861.54/25 => x= 8.63 . The dimension will be then Horizontal: 4 * 8.63 = 34.5 and Vertical : 3 * 8.63 = 25.8 . If your resolution is 1024x768 then in Horizontal there are 1024/34.5 pixels/cm and in vertical 768/25.8 pixels/cm . That means ~30pixels/cm for both dimensions.... If you want to have a square cm on your screen with its top left corner on 512,384 then you will have to add this in your script (if it is a 17" monitor @ 1024x768): PixelChecksum ( 512,384,542,414) I hope that helped a bit..... Of course there is an easier way to use AutoIt Window Info and use the coordinates it shows by "drawing" an imaginary rectangle and write down the numbers.... But I just had to show off... C ya

I see your point... I was wondering if there could be ,technically, an "adaptor" exe AutoIt could use to access a 64-bit dll... I mean an exe or dll AutoIt could use and then in its turn access the 64-bit dll... Could that be applicable or i'm just talking bulls**t? thanx for your time... C ya

When i said x64 i meant the 64-bit Version of windows ... Is x64 something different? Sorry if i 'm mistaken... I was talking about winrar's Rarext.dll(122Kb) and Rarext64.dll(42Kb). You can check it on your own.... When i said RunDll64() I meant DllCall64()... WTF what was I thinking? I was a bit hasty....

Thanx for the reply jpm . But is it the executable that is 32-bit that causes incompatibility or the way autoit uses to access the dll? Would it be possible that in the future this would be solved (lets say a rundll64() command)? I saw some dll's of a program that had 2 versions of the dll .One for 32-bit and for 64-bit windows. I noticed that the first one was around 160kb and the 64-bit version was around 50kb... So it is sure that dll's must have a different structure.... Take a look in this matter.... I think a full windows 64-bit compatibility would be good since people are starting to use them more and more... C ya

I have made simple proggie (NvTempLogger,check sig) and someone who tried this in x64 told me that it doesnt work right.... I dont know exactly yet... But my question is : Are the AutoIt executables compatible with x64 enviroment? The only external call that i use is DllCall in Nvidia's dll... Thanx, C ya

There is a new version out(V3.0). Check 2nd post for changelog and downloads...Worshippers proceed...

An experienced user in the particular forum(Guru3d) told me that the specific user might be lying just to draw attention... I dont know... But i was a little sad cos its such a disgrace to be new in a forum and some thousands of members thinking of you as a hacker.... Anyway, thanx for your replies... C ya

I think there was something like a petition towards a company that someone started about Autoit... Any info?

I posted my NvTempLogger proggie in a forum and someone said that Avast AntiVirus detected a trojan and a keylogger... So Autoit is blacklisted... What can we do about it? It's a shame people to think that everyone's decent effort to make a program to get the label of a "hacker"... So i'm waiting for suggestions to prevent that.... C ya

I tried this : $test=DllStructCreate("dword;dword;uint;uint;uint;dword;char[64];dword;dword;char[256];uint[2];char[64];dword;dword") DllStructSetData($test,2,$GUI) DllStructSetData($test,3,@autoitpid) $test2=DllCall("shell32.dll","int","shell_notifyicon","int",2,"ptr",DllStructGetPtr($test)) but no luck... it seems that the shell_notify icon is not recognizable... i tried "notifyicon" and sh_notifyicon" too....

I want to make my program run without showing on the taskbar but tray only... I have found this in MSDN but in the NOTIFYICONDATA structure asks for an ID and hwnd ... I have the hwnd but what about the id? Does anyone know how to solve this? Or at least have another way to do this? Thanx in advance. C ya

hahaha... busysignal... You shouldnt try too much.... Check my sig.... about the program for betas.... Thanx theguy0000 for your comment....

hand in the link to the msdn page you say....

The [2] parameter is indeed interesting.... There are many structures that use sub structures in MSDN.... Very useful.... C ya

My estimation is that it would work the same...au3 files are txt files with different extension.... So use the classic FileWrite() and FileWriteLine()... BTW: "The .au3 file included is the source, and can be opened with any text editor. " You said that on your own,in your sig.... C ya

You dont show us where you use the $v_FTx structures.... You tell it to get the pointer of this structures but i dont see them called by any dll or how you fill them...I believe they are the FILETIME structures huh? Have you tried to use DllStructGetData instead of DllStructGetPtr? Or try to use in your $v_Struct "long_ptr" or "int_ptr" instead of simple "ptr"... Play with these and tell me.... EDIT:Typos.... C ya

Thanx busysignal...It is implemented in the new beta too, 1.71.

I see that u have forgotten to use an extended style in your skin script. In basic_skin.au3 if you use : $menubar=GUICtrlCreatePic ("menu_bar.bmp",0,0,320,24,-1,$GUI_WS_EX_PARENTDRAG) instead of : $menubar=GUICtrlCreatePic ("menu_bar.bmp",0,0,320,24) Then you will have a smooth window movement and without having to play with MouseGetCursor(). $main_gui=GUICreate ("Your App",320,200,-1,-1,$WS_POPUPWINDOW) ;"Your App" defines the title of the GUI form. GUISetState(@SW_SHOW) $button_close=GUICtrlCreateButton("",290,0,24,24,0x0080) GUICtrlSetImage ($button_close,"menu_close.bmp") $button_min=GUICtrlCreateButton("",260,0,24,24,0x0080) GUICtrlSetImage ($button_min,"menu_min.bmp") $menubar=GUICtrlCreatePic ("menu_bar.bmp",0,0,320,24,-1,$GUI_WS_EX_PARENTDRAG) GUICtrlCreatePic ("menu_down.bmp",0,195,320,5) GUICtrlCreatePic ("menu_sides.bmp",0,24,4,200) GUICtrlCreatePic ("menu_sides.bmp",316,24,4,200) GUICtrlSetTip ($button_close,"Closes the application") GUICtrlSetTip ($button_min,"Minimizes the application") GUICtrlSetTip ($menubar,"Hold the primary mouse button to drag the window.") While 1 $msg = GUIGetMsg() If $msg=$button_close Then Exit If $msg=$button_min Then WinSetState("Your App","",@SW_MINIMIZE) ;~ $mouse_data=GUIGetCursorInfo ($main_gui) ;~ If $mouse_data[2]=1 AND $mouse_data[4]=$menubar Then GUI_POS() Wend ;~ Func GUI_POS() ;~ While 1 ;~ $mouse_data=GUIGetCursorInfo ($main_gui) ;~ If $mouse_data[2]=0 Then ;~ $mpos=MouseGetPos ( ) ;~ ExitLoop ;~ EndIf ;~ Wend ;~;these two values:320 and 200,corresponds to the size of GUI form. Change according to the size of your GUI. ;~ If $mpos[0]>@DesktopWidth-320 Then $mpos[0]=@DesktopWidth-320 ;~ If $mpos[1]>@DesktopHeight-200 Then $mpos[1]=@DesktopHeight-200 ;~ WinMove ("Your App","",$mpos[0],$mpos[1]) ;~ EndFunc C ya

Check my sig about interesting info about object viewer that is implemented with MS Office.... Bear in mind that the object might be "ShockWaveFlash.Application" for instance... You might find more with the Office object viewer.Moreover someone in scripts and scraps has published a UDF that manipulates Flash objects... It might be a good reference on how he calls the objects... Search... C ya