Recommended
Today’s guide is designed to help you when a system error occurs. Code 1400. The error code for an invalid window handle. g.Windows CSP reported error: Invalid window handle. Error code: 1400 Although we investigated the complication further, we did not find any underlying causes or similarities, such as a specific document reporting the issue.
You posted the best batch code, but not the actual key, the relevant part. Specifically, our implementation of your exposure is xOnAsyncRequestDone (unless the handler / method literally calls the protocol method you posted).
This system works in a TMySynHTTPAsync thread condition, and depending on the behavior you are sending, especially the one that Synchronize fixes your problem, it is highly likely that some actions in this event handler will create a window pen.
This window handle is then owned by the HTTP Async thread, the careful main thread of the application (sometimes called the “VCL thread”) that usually gets the job done. When your application exits, some vcl threads do some final cleaning of the house, destroying objects and windows, etc. As long as one of these windows is being created by another thread, they will cause problems.
Window handles are directly owned by the thread on which they were created. You cannot create a handle window using one thread and then destroying that thread in another.
What to noteThe flax on this website is that window handles can often be generated indirectly in the VCL. You will not necessarily see a categorical creation of a control that recognizes the creation of a base window handle. It’s easy when it comes to normal window handles, only to be really created when needed. Likewise, changing the properties of the responsible user can cause the VCL to experiment with recreating the window to monitor and destroy the current window next to the process. Follows
It is noteworthy that these mechanisms are very sensitive to problems that may arise. The second VCL methods are called from threads other than the VCL thread. This is why you are being told here that “the VCL is not thread safe.”
The safest way to succeed is to manipulate VCL objects only from code running in the VCL thread itself.
Synchronize With Rescue
The mechanism you are calling due to using Synchronize actually works to determine that the method you aresynchronize is done in the VCL declaration. If it can create a window handle, then in case a vcl thread comes up later that can destroy that window handle, it is certainly completely free, assuming it actually creates it.
More Options
The Synchronize mechanism is an interesting way to solve (today) problems with the angular platform, and so it could be an attempt to exaggerate in this case.
If you’re on Windows, a possible solution to this problem might be to take advantage of the fact that some windows allow threads to send (or post) warnings to windows in other messages. In this case, if messages acquired from these windows are processed by the careful thread of that window, just like all other messages with these windows. that is, someone cannot end up interrupting a single “click” message received by Window That by suddenly jumping over it to perform a notification from the thread. Note that the message must remain online as long as the sides of the window are aboutthis click message is fired. For instance. May
You think about it given that the “sync” system is “built in” when you need an operating system.
So, for research purposes, during initialization, you can pass a window handle to a specific form (or control, or whatever has a window handle) into your asynchronous HTTP stream and identify another VCL window that Request wants to receive … full warnings ”or other warnings from the stream. String can then send notifications to window frames dealing with PostMessage , also known as SendMessage , whether you are in a condition or declared during Override the WindowProc a warning handler.
When a thread uses SendMessage () to send a notification, it will be completely suspended and must wait for the message to be received and saved by the window (on the VCL thread).
Recommended
Is your PC running slow? Do you have problems starting up Windows? Don't despair! Fortect is the solution for you. This powerful and easy-to-use tool will diagnose and repair your PC, increasing system performance, optimizing memory, and improving security in the process. So don't wait - download Fortect today!
If a thread uses PostMessage () , the message is sent asynchronously, or the thread can continue working with others without waiting. Then The VCL thread retrieves the message and processes it.
No Recommendation
This does not mean that I would recommend this alternative in this case. While this article shows it, it might still be appropriate because it looks and looks like a simple shutdown message in this case, although there is no better understanding of your needs. Incredible specifics, however, it is impossible for you to help tell yourself what works best.
I just insist on pointing out that alternatives exist and that the key to safe and reliable streams is understanding the principles, not to mention the mechanisms involved.
Speed up your PC today with this easy-to-use download.
