Leaderboard

Greetings to all, Geodetic (newcomer) here, I have been putting together an application with a help file, and hit walls when it came to integrating help! A search of the forums turned up some hints, but also a lot of problems. So my last little while has been involved in putting together my HtmlHelp UDF - a fairly complete UDF for implementing help in your AutoIt applications. It provides functionality for Help file tab control (Contents, Index, Search) displaying topics by ID or by URL (in the CHM file) Popup creation and control etc. I have included some example files as well, but the real package is a little to large to include here, so you can download it from my personal site. The download link is here. Sorry, this link has been void since Shaw (my Internet provider) retired (like in Blade Runner!) personal webspace. Hope some find this useful! HtmlHelp UDF.zip Update (2021-01-25) I have updated the UDF (almost no changes to the actual UDF au3 file) as a kit, which includes a real AutoIt demo, detailed (compiled HTML) help file, original (but modified) sample files, more information and a few tools. This kit should be used instead of the above UDF link. The new demo and help file should simplify understanding how to implement help! I have not talked about actual creation of compiled HTML help - that is a topic best left to the user, particularly concerning the ancient HTML Help Workshop (compiler). It's old, but it's free, and it works! I'm happy to see that this post is now listed on the Wiki UDF page! - Allen AutoIt Html Help UDF Kit v1.3.zip

Very nice/useful UDF!! I'm curious why there is no response for such long time. It's also very handy as tutorial about HTMLHelp (CHM) background for developers. I will definitely use it one day ... It's question if this UDF should be include in standard includes ... Just one possible problem could be with Send() for Alt+underscored letter used in _HH_DispSearch(). I doubt if this will work on non-english Windows where can be underscored diferent letters.

The way the run statement was used it never worked with a program with spaces in the path or filename. I've updated the UDF to get rid of this bug. Thanks for pointing me to this error!

The directory where the script is located can be retrieved using macro @ScriptDir Edit: Too late

@ScriptDir?

If you're using loop (for example: for ... next) you can use "continue loop" or maybe "Return" if you're in a function

Learn about arrays, there is the wiki entry as well as the help file documenting usage. Good luck. My advice (though you don't have to take it) try to avoid using ProcessClose, instead obtain a window handle of the PID (process identifier) and send the WM_CLOSE message or use WinClose. Search the Forum for obtaining the PID from the window handle.

Maybe try... ControlTreeView('[CLASS:AlgFrame_MainWindow]', '', '[CLASS:SysTreeView32; INSTANCE:2]', 'Check', 0) ; You might need to change the index. Edit: Oh and welcome to the Forum, just saw the rest of the code and seems you know quite a bit already. hmm, dunno if that code above will work then?!

Good practice is that your application controls displaying error messages. System does it and will do it only if you fail to handle critical type of errors. This is done by calling SetErrorMode function as one of the first things you do in the script if there is even a remote possibility critical error will occur. See this example: Global Const $SEM_FAILCRITICALERRORS = 1 ; This is the line. You are telling: I'll handle possible displaying of critical errors myself SetErrorMode($SEM_FAILCRITICALERRORS) ConsoleWrite(FileOpen("A:") & @CRLF) ; This line would create system's critical-error-handler message box for my system if I haven't called SetErrorMode passing SEM_FAILCRITICALERRORS argument Func SetErrorMode($iMode) Local $aCall = DllCall("kernel32.dll", "dword", "SetErrorMode", "dword", $iMode) If @error Then Return SetError(1, 0, 0) Return $aCall[0] EndFunc