Hello Support,
In 14.1.4 I have problems with "Control has no parent window" (in 14.1.3 everything is ok).
Unfortunately, I was unable to create simple app reproducing the problem.
Please see the attached video.
Best regards,
:76a61d4d KERNELBASE.RaiseException + 0x48
Vcl.Controls.TWinControl.CreateWnd
cxControls.TcxControl.CreateWnd
Vcl.Controls.TWinControl.CreateHandle
cxContainer.TcxContainer.CreateHandle
cxEdit.TcxCustomEdit.CreateHandle
cxDropDownEdit.TcxCustomDropDownEdit.CreateHandle
Vcl.Controls.TWinControl.HandleNeeded
Vcl.Controls.TWinControl.GetHandle
Vcl.Forms.TCustomForm.SetFocusedControl($80343F0)
cxContainer.SafePassFocus
cxContainer.TcxCustomPopupWindow.CloseUp
cxGridCustomTableView.TcxGridFilterPopup.CloseUp
cxContainer.CloseUnrelatedPopupsOnMouseClick(1445946,(539, 283),513,False)
cxContainer.cxContainerMouseHook(0,513,204798328,0)
:0069c2dd TdxSystemHook.ProcessHookProcs + $55
:0069c09f dxSystemMouseHook + $1B
:7643941f ; C:\WINDOWS\SysWOW64\user32.dll
:764393a6 ; C:\WINDOWS\SysWOW64\user32.dll
:76446b97 user32.MonitorFromWindow + 0xa4
:7726eed2 ntdll.KiUserCallbackDispatcher + 0x2e
:7643840f ; C:\WINDOWS\SysWOW64\user32.dll
Vcl.Forms.TApplication.ProcessMessage(???)
Hello Piotr,
We, indeed, see that the new VCL 14.1.4 code is present in the call stack info you provided. However, we were not able to reproduce the problem using our demos. I see that you are using the grid's locked state image to perform filtering, but my efforts to replicate the erroneous behavior with this image were not successful. If it is impossible to provide us with a small demo, perhaps, you can simplify your real project to localize the problem. Reset all event handlers in your application. If the problem is gone, set them back one by one and see when the problem returns. If this does not help, remove all controls one by one, and test your sample at each step, until the problem is gone. As a result, you will have a small sample, illustrating the issue. This approach helps me in most difficult cases, so I believe it will help us in this scenario, too. I am looking forward to your feedback.
Hello Paulo,
Thank you for your response.
I have tried the solutions proposed by you without success. The only thing that solves the problem is to set property OptionsBehavior.AlwaysShowEditor to false.
In addition, I noticed that the problem occurs only when the active record (active before filtering) is not present in the filtered data.
Best regards,
Ok, reproduced :-)
Please see attached project and video.
Best regards,
I have reproduced this behavior. We will examine it and get back to you once we have any results or need additional information. Thank you for your patience.