deefburger

Thank You. I could control the location of execution all the way down to the machine by recording the IP address of the sender and dropping a cookie.... or compile for use on That machine only using info gatherd durring "registration" The registration code then sets a Reg value the new compiled code requires to execute. The new code is then made available for download..... Ahh the brain is buzzing now!

Perhaps "GUIGetCursorInfo ( [winhandle] )" I would test for the mouseclick, and then when a positive result was returned, read the coordinates and the control handle using this func. As far as the game clicking goes I've become a bit of an expert! I've written autoplayers for a couple of online games and encountered a couple of problems that I never expected to see! Method one is to simply use the absolute screen coordinates and click "there". This is a very reliable method so long as the windows open in the exact same place every time. Open the program you want to click in, and let stay where it is! Use the "MouseClick()" func for this. Method Two is to use "ControlClick()" I have found that this method sometimes dose not work because the controls, though visible to the eye, are hidden or inactive when not expected, or behind other active or inactive controls. When scanning a window in AU3Info, Take very special care to "look between the cracks" of the controls you identify. I found in one case a collection of 6 small buttons lined up like a wall of bricks, and behind them were the controls I needed! Three larger buttons lined up along the center of the "Wall". In AU3Info, I noticed, by chance, that the info changed "between the cracks". these were the Background buttons. I hope this helps you out. deefburger

Hi Jon, I just found this post looking for an answer to my problem of creating and implementing an activation code for a compiled script. I'm writing them all the time now and I (and my clients who pay for them), don't want them to be useable off site, or I want a full version to work from a trial after the code is entered. I would like the code to be different depenting on the user but be able to compile the same script and setup for multiple users and multiple codes. This way, I can track the versions and clients who should have the program and those who do not. Also, I would like to have the trial version fail after a specified number runs. Can you help? Thanks, Deefburger

UUUUUG! Some times the Obvious is so obscure! Thanks

Hi, I'm Getting the same error even with this simple script: Dim $testarray[64][9] For $x = 0 to 64 For $y = 0 to 9 $testarray[$x][$y] = $x + $y + 1 MsgBox(0, "TEST", "Element " & $x & "x" & $y & " is " & $testarray[$x][$y], 2) Next Next As soon as it reaches element $testarray[0][9] which sould get the value "10" it exits with the same error.