Re: Need help resolving modeless dialog issue

I'll try to answer the best that I can in sequential order.

Unfortunately, AliR, I can't. The entire project is quite large and
requires the use of an external security keys and dlls. I'm only
working on a small portion, largely limited to this small portion and
what it does, with the exceptions of being able to inject small
amounts of code to open the window, etc

As to the rather large initDialog, I suppose I stated that somewhat
misleading. The number of variables isn't that large, I'm currently
populating a keyword map inside of it (shortly to be moved to another
method, anyway).

I've gone through, and placed messages everywhere, overrode OnCancel,
OnClose, and PostNcDestroy with messages, and these do trigger
correctly when I close the window manually. I get no such message
when the first window, which does flash up for the tiniest portion of
a second. So I'm pretty sure it's not catching a rogue termination.

The idea of showing and hiding occured to me, and due to a second
problem I may persue that, but for now, fully closing the window upon
closing is ideal. The reason is this is an interactive panel that is
part of a larger program that allows multiple user permissions, and
forcing the window to open and populate it's members with only what is
applicable to that user level was desirable. I'm sure this can be
replicated upon showing the window, and it's something worth
considering. Also, allowing multiple editing windows might not be a
bad thing in this situation.

Hence, if it's not the problem, I'd like to keep multiple windows at a
time. If that's the problem though, I'd rather limit to one window
than have the user think the program is broken. I'll keep trying, I
think it may be something internal to our project (but not my window,
though that's always a possibility), and our graphics libraries. It
just doesn't seem like that would interfere with a modeless dialog
window.

Cheers,
~Scoots