Re: Floating window beside the main app window
Considering your worker thread already does procedural work,
redesigning it to be event-driven seems the bigger evil than
moving your window to the main thread. However, there's
a third option - create a new thread with the sole purpose of
hosting your window. I wouldn't recommend it long term, but
might do in a crunch... Long term all UI must be on the same
thread.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Victor" <big.boss@chefmail.de> wrote in message
news:1182864224.969557.127000@m36g2000hse.googlegroups.com...
Thank you, guys!
Well I admit that it is far not the best way to place the floating
window -- certainly, it is worth to check if it may be done
differently.
This is my first exercise to do it; and it was not required - or even
known - at the beginning of the project.
This window should visually display some data that the worker thread
receives from a network and may disappear when the thread exits -
that's why placing the creation of the window and its handling it the
thread seemed to me a proper place.
The question is : which way is less expensive now - to make the window
normally functioning on the place where it is right now or to move it
elsewhere? The both ways are unknown ares for me. So I would first try
to achieve the goal as is intended originally : or may be it would be
too goofy ? - could anybody access it?..
@Igor :
Do you mean a construct like this :
TranslageMessage....DispatchMessage in the calling thread?
Regards
Victor