🚀 go-pugleaf

> It is not.  However, your form's destructor should still execute properly.
> All Application->Terminate() does is calls PostQuitMessage() which posts a
> WM_QUIT message to the message queue, nothing else.  There are other
system
> messages associated with system logoff/shutdown that the VCL does respond
to
> as well, so it can still clean up after itself properly.

I'll have to do some more testing but it doesn't seem like the dtor is being
called.



> > This is actually a control application and it
> > needs to run without interruption if possible.
>
> Then I suggest you re-write the core of the application into a true
non-GUI
> service app, and then move just the GUI portions into a separate app that
> can communicate with the core service via IPC (inter-process
communication,
> such as TCP/IP sockets, named pipes, RPC, etc.) when needed.

That's about what I was thinking.  There is a fairly good division between
control code and
GUI code and we also use a remote GUI that works over TCP packets so it
shouldn't be
so difficult to deal with it.  The app is eventually going to be run on an
xp embedded target.  In that case, we can limit what windows will be doing a
bit.
We've been waiting for Siemens drivers that work with XP but I think they're
out now.

Thanks for the feedback.