Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-06 Thread Hans-Peter Jansen
On Sunday 05 October 2003 19:58, Hans-Peter Jansen wrote: > when calling qApp.{quit,exit}() methods? BTW: is it expected, that > they _return_ to the calling context? At least, I didn't. Silly me. It is expected, that they return, as noted in Qt docs. Sorry, Phil. Pete _

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Hans-Peter Jansen
On Sunday 05 October 2003 16:20, Sundance wrote: > I heard Hans-Peter Jansen said: > > Erm... I happen to have another question... Exception handling > while constructing the interface works fine, but I've got a problem > with the event loop. While it is running, it'll drop all the > exceptions sil

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Sundance
I heard Hans-Peter Jansen said: > Just close()ing the main widget should do the job nicely, as long as > the exception doesn't occur in the ctor/dtor paths of the main > widget. Okay, danke schon! Erm... I happen to have another question... Exception handling while constructing the interface wo

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-05 Thread Hans-Peter Jansen
Hi Sundance, On Sunday 05 October 2003 04:43, Sundance wrote: > I heard Hans-Peter Jansen said: > > Conclusion: beware from using qApp.quit(), or even sys.exit(0) > > without thinking twice. There are almost always better ways to > > close a PyQt application. Use them. > > This interests me. I've

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-04 Thread Sundance
I heard Hans-Peter Jansen said: > Conclusion: beware from using qApp.quit(), or even sys.exit(0) > without thinking twice. There are almost always better ways to close > a PyQt application. Use them. This interests me. I've been trying to write a clean exception handler around the event loop, so

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-04 Thread Hans-Peter Jansen
On Saturday 04 October 2003 11:17, Phil Thompson wrote: > On Saturday 04 October 2003 12:56 am, Michael Andrews wrote: > > I don't know if anyone else saw this article (I found the link > > from the Python Daily URL): > > > > http://www.dalkescientific.com/writings/diary/archive/2003/09/27/ > >Pyth

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-04 Thread Phil Thompson
On Saturday 04 October 2003 12:56 am, Michael Andrews wrote: > I don't know if anyone else saw this article (I found the link from the > Python Daily URL): > > http://www.dalkescientific.com/writings/diary/archive/2003/09/27/PythonCard >.html > > Most of the article talks about wxWindows and conclu

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-04 Thread Simon Edwards
On Saturday 04 October 2003 01:56, Michael Andrews wrote: > I've seen problems with my apps compiled with Qt 3.2.x (I don't even > know if it is the same problem); but is this a wide spread problem? In > other words, are other PyQt application developers seeing these > problems? I've only ever se

Re: [PyKDE] Web article on wxWindows and PyQt

2003-10-03 Thread Richard Jones
On Sat, 4 Oct 2003 09:56 am, Michael Andrews wrote: > "PyQt has its own set of problems, like the core dumps which arise from > deleting objects in the wrong order. (There was one talk using Qt. The > demos kept getting a core dump on exit because the code didn't ensure > qtApp was deleted last.)"

[PyKDE] Web article on wxWindows and PyQt

2003-10-03 Thread Michael Andrews
I don't know if anyone else saw this article (I found the link from the Python Daily URL): http://www.dalkescientific.com/writings/diary/archive/2003/09/27/PythonCard.html Most of the article talks about wxWindows and concludes that "... wxPython even now just aren't there yet." However, at the