Quote:
1) I am struggling with getting a single client to be associated with and docked with two different top-level host windows
You can do this. Just register dock client with new host each time its created. It must be repeated as host hwnd will be different. Alternatively you can change module to compare class instead of hwnd. If you can't control Host creation or you are not notified about it, then simple timer will do (although ideally, dock should be able to recognize new host). When time comes to devote my time to this module I will probably make this feature.
Quote:
2) I am also struggling with having a host control that is not a top-level window ....... I suspect that your hooks are for proper top-level-window related callbacks, and not for control-level callbacks. Is this an accurate assessment?
Yes, hooking controls isn't supported. The single line is responsible for this that returns from module when it detects notifications about child windows. You can change this. However, keep in mind that AHK is problematic ( a lot ) when dealing with functions running on message-like frequency. Since Dock monitors entire system, its notification function will be called by the system *a lot* (for each child, top level, tooltip and so on.. window created or moved). I was returning control to the script ASAP if window is not top level for the sake of CPU utilization and notorious problems with criticial command, message skipping and function reevocation. Perhaps it can be done better although Dock module is short peace of code where every single line is crafted over months to produce the best effect (and its still not perfect). AHK changed a bit since then so its time to update it and maybe support child controls hooking.
Quote:
The goal is to dock an .ahk gui to a non-ahk client (child?) window that is docked inside of another Win32 application.
This may be done now (I am not sure how good it will be). You can use T dock to put AHK gui ontop non-ahk gui. Then you need timer to check if control is moved and readjuce the dock definition. If control is not moving frequently it will be OK.
This is the important part of the module:
Code:
Dock_HookProc(hWinEventHook, event, hwnd, idObject, idChild, dwEventThread, dwmsEventTime ) {
local e, cls, style
if idObject or idChild
return
WinGet Style, Style, ahk_id %hwnd%
if (Style & 0x40000000) ;RETURN if hwnd is child window, idChild may be 0 for some children!
return
WINGETCLASS, cls, ahk_id %hwnd%
if cls in #32768,#32771,#32772,#32769,SysShadow,tooltips_class32
return
I pasted part that is responsible for fast return and you can see that function returns when it encounters Child or Object.
This is the part of the code from private Favmenu version that has multiple hosts.
Code:
Dock_HookProc(hWinEventHook, event, hwnd, idObject, idChild, dwEventThread, dwmsEventTime ) {
local e, cls, style
if idObject or idChild
return
WinGet Style, Style, ahk_id %hwnd%
if (Style & 0x40000000) ;
return
Dock_HostID := hwnd
gosub Dock_GetHandle
......
Dock_GetHandle:
if FavMenu_DialogGetActive() {
Dock_HostId := Favmenu_dlgHwnd
return
}
Dock_HostId := -1
return
In it, FavMenu_DialogGetActive checks active window to determine if its the window it handles. If it is , i set Dock_hostID to handle of the dialog so that favmenu icon can be docked as 4th button in the dialogs tittlebar. Favmenu monitors 7 types of dialogs.
I hope I helped.
Login
Register
FAQ
Search
