Leaderboard

New version - 13 Jan 2019 - Added: 2 new functions to hide/show and existing marquee. New UDF and example script in zip format: Marquee.zip As always, ready for compliments and/or complaints! M23

#RequireAdmin #include <ButtonConstants.au3> #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> $main = GUICreate("", 317, 317, 1030, 115, $WS_POPUPWINDOW ,$WS_EX_TOPMOST) $help = GUICtrlCreateButton("", 227, 3, 24, 24) GUICtrlCreateLabel("", 0, 0, 222, 30, -1, $GUI_WS_EX_PARENTDRAG) GUISetState(@SW_SHOW) $helpwindow = GUICreate("", 317, 317, 1030, 115, $WS_POPUPWINDOW ,$WS_EX_TOPMOST) $ok = GUICtrlCreateButton("OK", 161, 277, 150, 34) HotKeySet ("{numpad9}", "MyExit") While 1 $msg = GUIGetMsg() Select Case $msg = $help GUISetState(@SW_SHOW, $helpwindow) GUICtrlSetState($help, $GUI_DISABLE) Case $msg = $ok GUISetState(@SW_HIDE, $helpwindow) GUICtrlSetState($help, $GUI_ENABLE) EndSelect WEnd Func MyExit() Exit EndFunc

That's easy: We're cheap lazy bastards so we use the free great tools to get our stuff done for us. Seriously: I am was using it "ages" ago for automating repetitive tasks and some major global unattended software rollouts.... and somehow like the abuse I get around here. 🙂 Jos

First declare the variable with or without initialization. Only then increment it. Local $NUMBER = 1 $NUMBER += 1

Local $i = 1 $i += 1

So the software should appear in either 32bit or 64bit key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall You should be able to use the InstallPath (not always set) or UninstallString to get the path of your file,

Whats the name of the application? Does it appear in Add/Remove Programs? Does it have a file extension associated to it?

What difference does it make if you're writing it now and AutoIt stops being supported? You can write a program in the first version of COBOL if you wanted to, as long as you still have the compiler for it, even though it's not still supported. Whether Microsoft's API calls stay the same isn't up to the developers of AutoIt, no one can predict that unless they work for MS. If they change, and AutoIt no longer works, then you'll have to find a new language to work in, 10 years from now. As long as MS doesn't change things too drastically, you can keep programming in the language until it doesn't work.

I'm not sure if this helps your issue, but you could try the MouseOnEvent UDF to detect if the mouse was clicked. You can customize it to do x action if your cursor is inside specific coordinates with WinGetPos() I understand you need the condition to be true only on double click. In this case, see my example below. #include "misc.au3" $X = MouseGetPos(0) $Y = MouseGetPos(1) $BorderLeft = 0 $BorderTop = 0 $BorderRight = @DesktopWidth $BorderBottom = @DesktopHeight While 1 If $X > $BorderLeft And $X < $BorderRight And $Y > $BorderTop And $Y < $BorderBottom And _IsPressed(01) Then _OnSingleClick() WEnd Func _OnSingleClick() Do sleep(1) Until not _IsPressed(01) Local $timer = TimerInit() Do If $X > $BorderLeft And $X < $BorderRight And $Y > $BorderTop And $Y < $BorderBottom And _IsPressed(01) Then _OnDoubleClick() Until TimerDiff($timer) > 500 ;Delay in milliseconds to wait for a second click before assuming the event was single click. EndFunc ;==>_OnSingleClick Func _OnDoubleClick() MsgBox(0, "All good Bossun.", "Double Click Detected! Exiting...") Exit EndFunc ;==>_OnDoubleClick

Try StringRegExp()