GUICtrlSetOnHover UDF!

[MrCreatoR]

UDF update!

History Version:

  Quote

[v1.7] - [07.07.2009]

+ Added _GUICtrl_SetHoverOnBackwindow...

----Allows to set the hovering mode:

----------$iSetBackWin = 1 (default) hovering process will proceed even when GUI is not active (in background).

----------$iSetBackWin <> 1 hovering process will NOT proceed when GUI is not active.

[BigDaddyO]

It doesn't work if i compile the script with the Obfusticator /striponly switch set.

I even tested it with the Basic GUI Controls Example.au3 and i get the same problem.

I'm using the v3.3.0.0

Any ideas?

Mike

[playlet]

---

Edited August 18, 2016 by playlet

[MrCreatoR]

UDF update!

History Version:

  Quote

[v1.8] - [28.09.2009]

* Few Global variables now have more unique name.

* Fixed an issue with false calling of function on PrimaryDown event. I.e when the user clicks on other place (not on the hovered control) and drag the cursor to the control, the PrimaryDown function was called.

* Due to (and as a result of) previous issue, the UDF now registering WM_COMMAND and WM_LBUTTONDOWN messages at first UDF call.

  Quote

Any ideas?

Yes, check it on Obfuscator side

[CosmicDan]

Apart from your UDF being absolutely amazing, I'm having problems with this. It seems to randomly crash when I call my Exit function (GUI running in OnEvent mode), I disabled every other 3rd-party UDF just to test it and it's definately this. It appears to happen more often than if I try and spam my custom Quit button ASAP (i.e. as soon as the GUI is SHOWn) and AutoIt just hangs and borks out with an AppCrash

How could I narrow down the cause of such a thing? It only happens when I click. I tried examining the UDF but it's over my head =\ maybe there is a way I can simply disable everything to do with LMB tracking, since I only use the hover functions...?

[Achilles]

I'm having problems with this.. I'm not sure if it's the latest beta or me using windows 7. However; It's not doing anything when I run any of your examples. To be specific; I run "Basic GUI controls example" and it will show the GUI, but nothing special happens when the mouse hovers over the items (just the usual effects). I know the latest beta is causing an error (doesn't stop it from running) because Opt("OnAutoItExit".. is no longer available. I changed that to OnAutoItRegister or something but still no luck.

Any ideas?

[CosmicDan]

  On 11/5/2009 at 7:59 AM, 'Achilles said:

I'm having problems with this.. I'm not sure if it's the latest beta or me using windows 7. However; It's not doing anything when I run any of your examples. To be specific; I run "Basic GUI controls example" and it will show the GUI, but nothing special happens when the mouse hovers over the items (just the usual effects). I know the latest beta is causing an error (doesn't stop it from running) because Opt("OnAutoItExit".. is no longer available. I changed that to OnAutoItRegister or something but still no luck.

Any ideas?

Works fine in Win7 x64 for me. I also can't reproduce that weird crash bug I was getting two posts up anymore so that's good. But yeah seems like this needs to be updated for newest beta or the beta is unstable somewhere.

[Onylove]

When I Obfuscated the script by this udf, It isn't worked and have a problem:

  Quote

-### Obfuscation Error: Found Eval() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(371,1) Warning for line:$sEval = Eval("sParam" & $i-1)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(383,1) Warning for line:Local $iRet = Execute($sCall_Params)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(390,1) Warning for line:$iRet = Execute($sCall_Params)

-### Obfuscation Error: Found Call() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_OnAutoItExit C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(412,1) Warning for line:Call($__GUICtrl_SetOnHover_sOriginal_OnExitFunc) -############################################################################################# -#### Obfuscator Found 4 Error(s)!!!! This means your script could have problems running properly. #### -############################################################################################# +> Obfuscator v1.0.26.13 finished obfuscating 6791 lines, stripped 12039 comment lines. created:C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\Demo_Obfuscated.au3

Please tell me the way to correct it. Thanks all. Edited January 10, 2010 by Onylove

[MrCreatoR]

  Quote

When I Obfuscated the script by this udf, It isn't worked

This issue have been posted already: #583537

[Onylove]

Uh, But still the error. and I can't Obfuscate. Could you check it again? :-s. THanks!

[MrCreatoR]

  Quote

Could you check it again?

What i should check, it's related to obfuscator, there is no errors in original script, right?

[Onylove]

I think this udf incorrected something. You use the Obfuscator.exe to Obfuscator by Command, you don't see the Error (and then, mouse over isn't hover). You use the AutoIt3Wrapper GUI to Compile AutoIt 3Script (download at http://www.autoitscript.com/autoit3/scite/), you'll see the error below:

  Quote

-### Obfuscation Error: Found Eval() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(371,1) Warning for line:$sEval = Eval("sParam" & $i-1)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(383,1) Warning for line:Local $iRet = Execute($sCall_Params)

-###2 Obfuscation Error: Found Execute() statement which will lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_Call_Proc C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(390,1) Warning for line:$iRet = Execute($sCall_Params)

-### Obfuscation Error: Found Call() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: __GUICtrl_SetOnHover_OnAutoItExit C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\UDFs\GUICtrlSetOnHover.au3(412,1) Warning for line:Call($__GUICtrl_SetOnHover_sOriginal_OnExitFunc) -############################################################################################# -#### Obfuscator Found 4 Error(s)!!!! This means your script could have problems running properly. #### -############################################################################################# +> Obfuscator v1.0.26.13 finished obfuscating 6791 lines, stripped 12039 comment lines. created:C:\Users\Le Quoc Nam\Desktop\vtc\Icons_Hover\Demo_Obfuscated.au3

Edited January 11, 2010 by Onylove

[wraithdu]

For the love...

Did you read the error messages? They are errors from Obfuscator telling you it cant obfuscate your script because of the use of the Eval(), Execute(), and Call() functions. These are unsolvable errors. You will NOT be able to obfuscate your script, end of story.

[MrCreatoR]

  Quote

I think this udf incorrected something

How come?

It passes the syntax checking?

[martin]

  On 1/11/2010 at 2:47 PM, 'wraithdu said:

For the love...

Did you read the error messages? They are errors from Obfuscator telling you it cant obfuscate your script because of the use of the Eval(), Execute(), and Call() functions. These are unsolvable errors. You will NOT be able to obfuscate your script, end of story.

But maybe you can exclude those lines from the obfuscation and the script will still be fairly well protected.

#Obfuscator_Off
 ;problem line or lines
#Obfuscator_On

[wraithdu]

With those directives it is very easy to break stuff. Reason is that the actual function won't be touched, but calls to it in other places in the script or calls it makes to other functions, will be obfuscated. The end result is the script tries to call a function by a name that doesn't exist (it has been obfuscated).

Edited January 12, 2010 by wraithdu

[Rawox]

I'm not 100% sure about it but it seems it only runs in 32bit mode.

I don't know of this is already noticed, but I thought I point it out anyway

[billthecreator]

  On 2/24/2010 at 7:11 PM, 'Rawox said:

I'm not 100% sure about it but it seems it only runs in 32bit mode.

I don't know of this is already noticed, but I thought I point it out anyway

yep, doesnt work on my 64-bit win7.

[Homes32]

  On 4/23/2010 at 9:32 PM, 'billthecreator said:

yep, doesnt work on my 64-bit win7.

same problem here. 32bit works great! 64bit is no dice though.

[MrCreatoR]

  On 5/19/2010 at 2:02 AM, 'Homes32 said:

same problem here. 32bit works great! 64bit is no dice though.

Strange, i don't find anything in the UDF code that can cause any problems under 64bit...