argumentum

#include <ButtonConstants.au3> #include <GUIConstantsEx.au3> ;;; https://www.autoitscript.com/forum/topic/213492-button-reacts-to-the-enter-key-used-in-an-input-box/ #include <GuiEdit.au3> Opt("GUIOnEventMode", 1) #Region ### START Koda GUI section ### Form= $Form1 = GUICreate("Test", 207, 369) GUISetOnEvent($GUI_EVENT_CLOSE, OnEvent_CLOSE) $Inp1 = GUICtrlCreateInput("0", 2, 19, 121, 22) GUICtrlSetFont($Inp1, 12, 700, 0, "Ubuntu Mono") GUICtrlSetOnEvent(-1, OnEvent_Inp1) $Edit1 = GUICtrlCreateEdit("", 3, 86, 201, 281) GUICtrlSetData($Edit1, "") GUICtrlSetFont($Edit1, 10, 700, 0, "Consolas") GUICtrlSetLimit($Edit1, 15000000) GUICtrlSetOnEvent(-1, OnEvent_Edit1) $BTN1 = GUICtrlCreateButton("TEST", 70, 0, 40, 16) GUICtrlSetFont($BTN1, 8, 700, 0, "Ubuntu Mono") GUICtrlSetBkColor($BTN1, 0x00F000) GUICtrlSetOnEvent(-1, OnEvent_BTN1) GUISetState(@SW_SHOW) #EndRegion ### END Koda GUI section ### ;" " While 1 Sleep(100) WEnd ;~ $nMsg = GUIGetMsg() ;~ Switch $nMsg ;~ Case $GUI_EVENT_CLOSE ;~ Exit ;~ Case $BTN1 ;~ GUICtrlSetData($Edit1, "Test" & @CRLF, 1) ;~ EndSwitch ;~ WEnd Func OnEvent_CLOSE() GUIDelete() Exit EndFunc Func OnEvent_Inp1() GUICtrlSetData($Edit1, "Inp1" & @CRLF, 1) EndFunc Func OnEvent_Edit1() ;~ GUICtrlSetData($Edit1, "Edit1" & @CRLF, 1) EndFunc Func OnEvent_BTN1() GUICtrlSetData($Edit1, "Test" & @CRLF, 1) EndFunc Also happens on event.

Do you use scaling due to your Monitor ? If "no", the real answer is "not yet" Looking at a HiDPI monitor is a mater of time. And seeing it in it own "max. resolution" looks very nice. So even if your project is for dark mode only, and the HiDPI is a "nice touch", the evolution of the HiDPI will be an inevitable thing that every year is more pressing. Ok, back to topic. hmm, I don't know. I don't think so. You're coding a UDF, not script per say. So no, the user can later add it to any folder the users wishes. If the DLLs you open are just for your UDF then you should name the variables something like "$__g_MyUDF_hDLL_ThisOne", so that is not going to match some other common name, and you do you own DLL cleanup of the DLLs your UDF opens.

#include-once ; #include "DLL_OpenClose.au3" #AutoIt3Wrapper_Au3Check_Parameters=-q -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7 ; this line shold be on every file to warn us of ... stuff Global $g_hGdi32Dll = DllOpen("gdi32.dll") Global $g_hUser32Dll = DllOpen("user32.dll") ; ..the same with all DllOpen() in the project(s) ; Cleanup OnAutoItExitRegister(__DllCloseAll) Func __DllCloseAll() DllClose($g_hGdi32Dll) DllClose($g_hUser32Dll) EndFunc That above I think is a good idea for this all encompassing ( dark mode / HiDPI ) project. Add #include "DLL_OpenClose.au3" as the 1st include on every script that uses them DLLs and, it'll be better.

..and am like "use #forceref to tell au3check..." and he's like "I have no experience with it". ..and in my head am like "just type it and press F1" So, it's not indexed in the help file, because is deep in "Autoit\Using AutoIt\AutoIt Syntax Checker (Au3Check)" and those files are excluded. Pressing F1 will not give you even a hint of #ignorefunc, #forceref or #forcedef -q : quiet (only error/warn output) -d : as Opt("MustDeclareVars", 1) -w 1: already included file (on) -w 2: missing #comments-end (on) -w 3: already declared var (off) -w 4: local var used in global scope (off) -w 5: local var declared but not used (off) -w 6: warn when using Dim (off) -w 7: warn when passing Const or expression on ByRef param(s) (on) The above is shown in SciTE's help file too because of "#AutoIt3Wrapper_Au3Check_Parameters" but also no mention of #ignorefunc, #forceref or #forcedef. Is not a utility that comes with SciTE. It should be fixed in the AutoIt help file. It should popup pressing F1 so that I can say: "RTFM"

not sure about anything because am just browsing, but I saw "_WinAPI_SetThemeAppProperties(0)" and thinking to myself am like "what if I add a button after ?, the whole gui is w/o theme now ?" and I thought of this: Func _WM_NOTIFY($hWnd, $iMsg, $wParam, $lParam) #forceref $hWnd, $iMsg, $wParam Local Static $iTheme ; argumentum Local $hWndFrom, $iIDFrom, $iCode, $tNMHDR, $tInfo, $tBuffer, $tBuffer2, $iCtrl $tNMHDR = DllStructCreate($tagNMHDR, $lParam) $hWndFrom = HWnd($tNMHDR.hWndFrom) $iIDFrom = $tNMHDR.IDFrom $iCode = $tNMHDR.Code Switch $hWndFrom Case $g_hDate ;thanks to argumentum for the code :-) Switch $iCode Case $NM_SETFOCUS $iTheme = _WinAPI_GetThemeAppProperties() ; argumentum ; Disable the visual theme when the DateTime control receives focus _WinAPI_SetThemeAppProperties(0) Case $DTN_DROPDOWN;, $EVENT_OBJECT_CREATE ; Apply dark colors when the calendar dropdown appears _WinAPI_SetWindowTheme($iCtrl, "", "") Local $iCtrl = _GUICtrlDTP_GetMonthCal($hWndFrom) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_TEXT, $GUIDARKMODE_COLOR_GUICTRL) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_TITLEBK, $GUIDARKMODE_COLOR_GUICTRLBK) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_TITLETEXT, $GUIDARKMODE_COLOR_GUICTRL) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_BACKGROUND, $GUIDARKMODE_COLOR_GUICTRLBK) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_MONTHBK, $GUIDARKMODE_COLOR_GUICTRLBK) _GUICtrlMonthCal_SetColor($iCtrl, $MCSC_TRAILINGTEXT, $GUIDARKMODE_COLOR_GUICTRL) Case $NM_KILLFOCUS _WinAPI_SetThemeAppProperties($iTheme) ; argumentum Case $DTN_CLOSEUP ; Calendar will closed EndSwitch EndSwitch Return $GUI_RUNDEFMSG EndFunc ;==>WM_NOTIFY because otherwise we may be introducing a bug.

I just changed again from "_WinAPI_GetSystemMetrics(7)" to "_WinAPI_GetSystemMetrics($SM_CXDLGFRAME)" because: "say no to drugs magic numbers"

I "fixed" this function as an example of how to go about it, because if you've never done it before, it could be a good example. Edit: found name of magic number

Jos made the SciTE and utilities, and is a godsend, because it'll show what could be a problem and often times is right. So, as a default you add "#AutoIt3Wrapper_Au3Check_Parameters=-q -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7" Once you run, or Ctrl-F5, the console will show a bunch of complains, of which some are of variables that are needed even if unused. For those you add "#forceref $MyVar, $MyOtherVar" but only if is a must, like in a GUIRegisterMsg() function. Don't go around just overriding a complain. If you use those, it'll train you to code better Disclaimer: Some of the code you've inherited is mine and to my defense, ain't got one. Is just ugly. But "do as I say not as I do"

add this to all your scripts: #AutoIt3Wrapper_Au3Check_Parameters=-q -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7 If needed, add these ( as an example ) : #forceref $hwnd, $iMsg, $wParam, $lParam Then you fix all the scripts ( yours and/or inherited ). Then start working on debugging, but not before that. ..argumentum walks away dropping the mouse on the floor as if it was a microphone..

..it shows fine. Then you click around and at times, it looses the coloring. Not always but I've seen it. ..and it goes like this: you click the date to open up, then you click the menu ( that you haven't clicked before ) and it paints w/o the coloring 🤔 Beta tester #1

Si, Ja, Oui oui The question is: do you know the intricacies of other languages 🤔 There are languages that are "right to left" and some that are top to bottom ?. I guess one of those who speak/type in that language would know better. So yes. It'd be beautiful to attend to all languages. I just don't know how. If one of those ( too strange to English speakers ) languages are brought up by a user, we'll discover it then 🤷‍♂️

..you win, I'll build a map. ( talking to myself )

Ok. A new day and a new way to look at it. No indexing because, am lazy by nature, but to my defense I think is not needed. We send "the word" to the help file and if not there, it'll click "Index" and look there. Is faster because everything is in the browser at browser speed. Less work in the script. Again, any questions, problems or wishes, post them here. AutoIt3HelpWeb(2026.02.28).zip Edit: Tested in WinPE and had to up the delay of "can't find it in tree" form 1 sec to 2 sec ; ..allow the tree to "build" the nodes, if not found in time, stop looking While TimerDiff($hTimer) < 1000 ; it may need 2 seconds, or 3 ??? for the "Index" to go back to "Contents" if it was there. So maybe an index will be welcomed in a slower PC 🤔 Y'all complain if it is a need. I don't think our PCs are that slow ( or we are that impatient ) ..also, I should have code a filter there like ;... in AHWD_WebServer.au3 Else AHWD_HttpSender($iSocket, "", "", "204 No Content") If StringInStr($sRequestTarget, "://") Then ShellExecute($sRequestTarget) EndIf ;... otherwise there may be ugly errors ..next version will fix that. Lets accumulate all the oops together

WinMerge is a good tool to compare files. Yes it was working before, hence the complain.

The menu drop down in SampleControls-Dark.au3 does not show dark as it did. Beta tester #1