Jump to content

Recommended Posts

Posted

In this update,
I refactored the keyboard navigation logic to make it cleaner and completely naturally.

What changed

Removed HotKeySet for TAB navigation
Now handles native control focus cycling naturally without any key hooking.

Replace with _WinAPI_GetFocus() 
A function inside the main loop compares the current focus window handle against the previous state.

Clean Visual States
It automatically detects when focus moves into or out of the fake combos (via TAB, Shift+TAB, or mouse clicks) and updates the active highlight state.
 

Thank you once again   :)
for the continuous feedback and support!
 

I updated the first post  with the new version.

I know that I know nothing

Posted

@ioa747 Hello :)
Glad you got rid of the HotKeySet for TAB navigation.
I got a question : is the script below the way to retrieve what is returned from Font_Dialog.au3 in light mode ?

#include <AutoItConstants.au3>
#include <GUIConstantsEx.au3>
#include <MsgBoxConstants.au3>

Example()

Func Example()
    Local $hGUI = GUICreate("Test Font_Dialog 0.21", 400, 250)
    Local $idTest = GUICtrlCreateButton("Choose Font", 20, 20, 100, 30)
    Local $iPID, $sRead

    GUISetState(@SW_SHOW, $hGUI)

    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE
                ExitLoop

            Case $idTest
                GUICtrlSetState($idTest, $GUI_DISABLE)
                $iPID = Run(@AutoItExe & " " & chr(34) & @ScriptDir & "\Font_Dialog.au3" & chr(34), _
                    @ScriptDir, @SW_HIDE, $STDOUT_CHILD)
                ProcessWaitClose($iPID)
                $sRead = StdoutRead($iPID)
                MsgBox($MB_TOPMOST, "Returned from Font_Dialog", $sRead, 0, $hGUI)
                GUICtrlSetState($idTest, $GUI_ENABLE)
        EndSwitch
    WEnd

    GuiDelete($hGUI)
EndFunc   ;==>Example

 

TestFont_Dialog1.png.d719fa1f0d859ddc3f0d20ea5e79638f.png

After that, I made another test and tried a single ConsoleWrite in Font_Dialog.au3

ConsoleWrite($aResult) ; without splitting it in Font_Dialog.au3

Then this is what could be used in the calling script, it may be more user friendly... or not :D

TestFont_Dialog2.png.f863a3b825e47dbf0a1a5d353116b050.png

"I think you are searching a bug where there is no bug... don't listen to bad advice."

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...