Re: UIThreads, dialogs & messaging problem
Simon L wrote:
3. I'm not even sure why you need a thread here, or why the dialog is
non-modal. Why not just use a timer and a modal dialog, if the user is
not allowed to do anything until he/she logs back on.
I've gone back to this a couple of times, and I've come up against
problems like menus not wanting to disappear (though why they do in
this case eludes me), wanting to create and show the modal dialog that
is already active and modal (does this not stop the message queue for
the window that launched the dialog?)
My messaging problem isn't one of losing the parameters I've realised,
but the whole message, which gets to OnPreTranslateMessage in the App
but not to my view...
Simon:
There's something odd here. A modal dialog should disable the rest of
the application for user input. Which is what you want, yes? And what do
you mean about menus not disappearing? Launching a modal dialog froma
menu handler is a very common thing to do: the menu disppears and the
modal dialog is shown.
Why do you expect your custom mwthod to go to the view? Are you actually
forwarding it? MFC does not route all messages, just WM_COMMAND messages.
I might suggest that you experiment with a brand new project, and try to
simplify the design of this feature.
David Wilkinson