> On Thursday 07 July 2005 15:01, Phil Thompson wrote: > >> The original proposal would cause problems in the following scenario... >> >> 1. One or more modal dialogs that are hidden when not used, rather than >> being re-created each time they are needed. >> >> 2. The dialogs are Python sub-classes of QDialog or the dialog has >> instance objects (ie. there are useful Python objects tied to the C++ >> instance). >> >> 3. No application references to the dialogs are maintained. The >> application relies on finding a dialog again by searching its parent's >> children. > > ....nor relies on the dialog staying alive to respond to events or > signals. > right?
Correct. >> This would seem to be an untypical way of doing things - is anybody >> going >> to shout that their 5 million line application relies on this technique? > > I *think* it should be problem-free, but Im not feeling confident about > being > able to reliably anticipate any problems. I would be happy to test if > there > was a patch for existing PyQt versions. I *think* it should be problem free as well - but I don't *know*. Particularly as we are getting towards the end of PyQt3's life and it hasn't come up before in the last 7 years. So why not just wait until PyQt4? I'll shout loudly if I add it to a snapshot. Phil _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
