🚀 go-pugleaf

"Stefano Bonifazi" <stefboombastic@email.it> wrote in message
news:4592e225@newsgroups.borland.com...

> Well it seems this time I get into something impossible to do :(

Apparently so.

> Impossible the console application should continue its work in spite
> of what my form does ...

Then you are running out of options.

> No the console application has a loop that does other than processing
> windows messages.. low level stuff with high priority

Then that loop will have to handle messages as well.  Or at the very least,
have your DLL export a function to process any pending messages in the
calling thread, and then the console application's loop can call that single
function periodically.

> If I have to start coding all the windows in WinAPI the wonder of
> borland vanishes and I'd better use the MS VC++

When it comes to working with the API directly, VC++ does not gain you
anything that Borland does not already do.  You will still have the same
amount of work in your code, so you may as well stick with the Borland
compiler if that is what you are comfortable with.

> But if I create a window inside a thread spawned by the DLL, cannot
> those messages be received by the thread provided that window has its
> message queue?

Like I said earlier, messages for a window can only be received by the
thread that created the window.  A window is tied to a specific thread.  No
other thread can receive messages for that window.


Gambit