Leaderboard

You know what they say, "Once you go cold, it never gets old"

Done. Thanks for that. Also, you know you spelt 'Edit' wrong in your edited post?

1) Descriptive topic isn't very descriptive. 2) Dafuq?

mmh, imho it's inconsistent behavior too... But in Haskell positive numbers shift and rotate to the left, whereas in MathLab it's the other way around, atleast for the bitshift function it is. Most languages use << and >> operators which arn't as implementation dependent or ambiguous. So yea... You could just say that AutoIt has character, like wine

You're all a bunch of necrophiliacs. Thread was dead for 5 years until resurrected yesterday.

as long as it doesn't involve keylogging or malware, and the tutorial doesn't breach the 'no reverse engineering' clause of the license, you should have no issues. (as far as written rules go) if you have breached the latter part, you can always rewrite your tutorial to use techniques which don't constitute reverse engineering. this is very commonly done by researchers. sneaky bastards.

Or using a 'flag' to detect a change in the input and run the function. #include <Date.au3> #include <EditConstants.au3> #include <GUIConstantsEx.au3> #include <WinAPI.au3> #include <WindowsConstants.au3> Global $__iLabel = -9999, $__iFlag = 0 Example() Func Example() Local $hGUI = GUICreate('Input Filter', 300, 30) $__iLabel = GUICtrlCreateInput('', 5, 5, 290) GUIRegisterMsg($WM_COMMAND, 'WM_COMMAND') GUISetState(@SW_SHOW) While 1 If $__iFlag Then $__iFlag = 0 _Change() EndIf Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop EndSwitch WEnd GUIDelete($hGUI) EndFunc ;==>Example Func _Change() ConsoleWrite('Change: ' & _Now() & @CRLF) EndFunc ;==>_Change Func WM_COMMAND($hWnd, $iMsg, $iwParam, $ilParam) #forceref $hWnd, $iMsg, $iwParam, $ilParam Local $iLoWord = _WinAPI_LoWord($iwParam) Local $iHiWord = _WinAPI_HiWord($iwParam) Switch $iLoWord Case $__iLabel Switch $iHiWord Case $EN_CHANGE $__iFlag = 1 EndSwitch EndSwitch EndFunc ;==>WM_COMMAND