2023-03-16, 12:15:03
(This post was last modified: 2023-03-16, 12:18:42 by jkirstaetter.)
Hello Wil,Thanks for quick response and handling.
Sure, will do.
However, it might take a bit time to isolate everything as we have several levels of class inheritance in our project.
Meanwhile, I got some feedback from another VFP developer Christof W. (Foxpert) that this could be related to the "form/window" handle that an ActiveX control might create and hence disables other parts. This could be helping for the modal form (WindowType):
(2023-03-16, 09:54:58)wila Wrote: For several of those we have issues logged already, but your main issue, for which you started the post - the focus issue - is new to me.
Can you create a small reproducible sample of this issue and send that by email?
That would help a lot in being able to reproduce it here and look into that.
Sure, will do.
However, it might take a bit time to isolate everything as we have several levels of class inheritance in our project.
Meanwhile, I got some feedback from another VFP developer Christof W. (Foxpert) that this could be related to the "form/window" handle that an ActiveX control might create and hence disables other parts. This could be helping for the modal form (WindowType):
Code:
* HWND des ActiveX Controls aus dem Activate des Formulares heraus aufgerufen werden.
*========================================================================================
LParameter tnHWND
Declare Long GetParent in Win32API Long
Declare Long EnableWindow in Win32API Long, Long
EnableWindow( GetParent(m.tnHWND), 1 )
Thanks in advance and best regards, Jochen
"The only frontiers are in your mind."
"The only frontiers are in your mind."