argumentum

All these WYSIWYG CHM compilers use the M$ workshop. So they are wrappers. The nice thing is the HTM output, and that, we can cook our own in AutoIt. The science behind it is the JavaScript that makes it all work together. If someone feels like tweaking all these to come up with something visually appealing that works by running a script ( because by hand is a "nothing burger" ) then we have something that will work consistently in building the help file. Then the WebView2 have to work with the AutoIt3Help, and since WebView2 is only the "browser", an HTM daemon serving these HTM files to WebView2 has to work with it all too. Press "F1" and AutoIt3Help tells the "HTM deamon" to tell the browser to goto "this page" ( or something like that ). It's an interesting adventure to take on, and a very welcomed product once up and running. Should post: now recruiting "front end", "back end" and "all ends" developer. Must have 30 years experience in: everything

( misunderstood the question )

...this ZIP ( down below ) is what my version of the web site would look like but is an alpha. The JS and CSS are the same. Just the HTM files are not in sync with 3.3.18.0 because is based on the current alpha. If you can use some of the code from it, have at it Then look at everything once you're back to your PC. None of this is final and nothing is just one file yet with @bladem2003's compilation. It will take some rewriting/coding to get there. Also, all these HTM should be loaded with a web server ( I use Apache ) and there are examples all over the forum ( from me too ) to make one with AutoIt. Loading HTMs as files will not allow some of the feature to work as coded. I did and the ZIP down below is what I did on my side, long before you came up with yours, ...that 'd like to merge but I don't have much time to "go at it", and "full speed ahead" is my only mode 🤷‍♂️ I like this type too but again, no time 😕 Ok, I'll leave it up to y'all. Make me proud ! 🥹 AutoItWebSite-v3.3.19.0-Alpha_r13287(argumentum).zip

..then I guess I should leave it alone for now because you are still working on it. When you feel that you're good with as far as you took it, I'll play with it. If you can take a request: make it "sync to toc" when an internal link is clicked, to mimic a CHM.

..did some patching too because I didn't like the red divider nor the white background. The colors around the files are going to have to be moved to the default.css to make it more flexible and be able to change "color modes" ( light/dark ) on the fly.

..and: "Click for more help" links to "https://kb.helpwaregroup.com/far/webhelp/search-help" that don't exist. Given that this is close to abandonware ( last update in 2019 ), the generated files will have to be patched for coherent functionality. We are responsible of whatever we host and can not claim that is not our fault because we are in the software business ourselves 😲

"FAR HTML is a free Windows application. A collection of help authoring and file utilities." Ok, free is good. Given that the software is free, I think that attempting an integration that generates this ( help file with index and search ) in the workflow of the AutoIt help file ( and web site ) will not be limited by licensing concerns. So, the web site wouldn't need much convincing to the higher ups ( you know who you are ). Now, CHM vs WebView2. CHM can run anywhere, WebView2 not so sure. ( I'd love to have a fully functional help file in WinPE 😍 ) Then we will have to come up with a AutoIt3Help.exe to work with the WebView2 version in local PCs. I guess that if we make an AutoIt3Help.exe script ( by we I mean you all ), am sure that it can be translated to C and have the alternate ( for now ) "local web help". Again, this forum brought about everything around and in the AutoIt distribution. So it'd be up to us forum members, to change the ways things are, that as always, change bring about some degree of resistance 🤷‍♂️ This is me thinking out loud. As always, "put your code where your mouth is"(tm) @bladem2003, nice going. Thanks P.S.: Everything that builds the help file and web site, needs to run from a command line.

#Region ;**** Directives created by AutoIt3Wrapper_GUI **** #AutoIt3Wrapper_UseX64=y #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI **** #include <GUIConstantsEx.au3> #include <WinAPIIcons.au3> ; _WinAPI_ExtractIcon #include <SendMessage.au3> ; _SendMessage ; System DPI awareness DllCall("user32.dll", "bool", "SetProcessDpiAwarenessContext", @AutoItX64 ? "int64" : "int", -2) Example() ; https://www.autoitscript.com/forum/topic/213458-guiseticon-dpi-bug/#comment-1549810 Func Example() ; Create a GUI with various controls. Local $hGUI = GUICreate("Example", 400, 400) ; Display the GUI. GUISetState(@SW_SHOW, $hGUI) ; set GUI icon ;~ GUISetIcon(@ScriptDir & "\app.ico") _WinSetIcon($hGUI, @ScriptDir & "\app.ico") ; set tray icon TraySetIcon(@ScriptDir & '\app.ico') ; Loop until the user exits. While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop EndSwitch WEnd ; Delete the previous GUI and all controls. GUIDelete($hGUI) EndFunc ;==>Example Func _WinSetIcon($hWnd, $sFile, $iIndex = 0, $bSmall = False) ; https://www.autoitscript.com/forum/topic/168698-changing-a-windows-icon/#findComment-1461109 Local $WM_SETICON = 128, $ICON_SMALL = 0, $ICON_BIG = 1, $hIcon = _WinAPI_ExtractIcon($sFile, $iIndex, $bSmall) If Not $hIcon Then Return SetError(1, 0, 1) ; https://learn.microsoft.com/en-us/windows/win32/winmsg/wm-seticon _SendMessage($hWnd, $WM_SETICON, Int(Not $bSmall), $hIcon) _WinAPI_DestroyIcon($hIcon) EndFunc ;==>_WinSetIcon Google is your friend. Actually @Nine is vs this: Edit: #include <windows.h> // ... inside your code, e.g., after CreateWindow or in WM_CREATE handler ... HICON hIcon = LoadIcon(hInstance, MAKEINTRESOURCE(IDI_MYICON)); // Load your icon resource if (hIcon) { // Set the large icon (appears in Alt+Tab, etc.) SendMessage(hWnd, WM_SETICON, ICON_BIG, (LPARAM)hIcon); // Set the small icon (appears in the title bar) SendMessage(hWnd, WM_SETICON, ICON_SMALL, (LPARAM)hIcon); }

tray looks better with just 64x64, let the OS / AutoIt do the resizing. au3.213458-guiseticon-dpi-bug.app_v2.ico And yes, @jpm should look at this. ( I don't know of a work around but there should be one on the _WinAPI_* side of things )

Yes, the tray icon looks better than the GUI caption's icon.

oh, don't make me get stated with what I take offence of !. 🤬 Actually, am not one to go for "I feel offended", as it does not attend to the matter in question. I don't feel offended. Can, and do, feel perplexed at certain train of thoughts..., but I take no offence. If you were to call me names, then, I'd ask what me being a "insulting word of choice" has to do with what we are discussing. If you feel you offended me then, you are pardoned

..then, mind the calculation ? 🤷‍♂️

What do ReDim to less than 1 entry do ?. I guess any script, UDF or not, can be baby-proof. But again, what is the use of declaring an entry of 0 ? @pixelsearch, if you edit __ArrayDisplay_SortArrayStruct(), and @jpm agrees, he'll use your version @IronFine, why do you need to ReDim $aArray[2][0] ?

I guess I could add a line to prevent code like that, not crash a script. Or I can ignore those that want to make a zero dimension Hey, divide by zero while you're at it

This is the 2nd time that I go to the download for it and there is no script file.