Quote Originally Posted by Niya View Post
No doubt.

techgnome even suggests that the entire owership chain gets disabled. While this might very well be true throughout all of Windows, it's really only a convention. You or I could implement a different convention if we wanted in our own applications. We could choose to disable all top level windows in the process or just the ones in the chain to which our modal window belongs.
Yes, I've done one, as commented here:

Quote Originally Posted by Eduardo- View Post
that's exactly what I do in a custom ShowModal procedure that I have in a component: If there is an active window (usually a form), I make the modal form owned by that form.

The purpose of my ShowModal procedure is to allow non modal forms to be displayed (like a toolbar or something like that) after a modal form is shown, and then bypass the intrinsic limitation that VB/Windows have.
I'll post it in the Codebank as soon as I finish other things.

Quote Originally Posted by Niya View Post
Hell, we don't even have to disable any window at all. The message loop alone would create modal behavior.
I have doubts about that: the other windows could be frozen if you don't allow them to be painted (and to process other messages).

Quote Originally Posted by Niya View Post
The point is, modality is not a property inherent to the window.
Yes, that's what I've been saying all the time in this thread.