Hi Fabian, No... The application I'm writing is not multithreaded (there are some areas where it is, but that is working fine)...
I suspect it has something to do with invalid/wrong parent windows. But I think it has something to do with having 2 modal dialog boxes open (ie. chained)... which I do have. My simplistic testing seems to indicate this is ok, but I guess in the real world this isn't advisable. I was mainly using modality as a focal point - which could I guess be achieved using the ownership rather than on modality. Input blocking would be a problem. Any ideas? Modality is rather too simplistically implemented in .NET. It would seem that you can't 'transfer' modality which is often the required behaviour (ie a modal dialog box, opens another dialog box which is modal) but not supported well in either .NET or Java. On 12/5/07, Fabian Schmied <[EMAIL PROTECTED]> wrote: > > > Firstly, has anybody experienced this sort of thing and how did they go > > about fixing it? I'm tempted to rip up all my modal dialog code and just > go > > modaless - and rely on callbacks and states rather than on deterministic > > 'blocking' and handle user input blocking myself. Seems a bloody awful > waste > > of time - to have to re-implement modality though. > > I have seen problems with dialog rendering (in Windows Forms) only in > two situations: > - Multithreaded UIs (without proper use of Control.Invoke) > - Invalid/wrong parent windows specified when showing the dialogs > > Does one of those fit in your situation? I'd guess it is the first one > - are you using multiple threads? > > Fabian > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > -- Cheers, Jason =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
