[PyKDE] QT/Mac to be licensed under GPL

2003-06-18 Thread Gordon Tyler
Hi all, I just saw this press release on Trolltech's site: http://www.trolltech.com/newsroom/announcements/0129.html Trolltech today announced that Qt/Mac will be released under the GPL (GNU General Public License) at Apple's World Wide Developer Conference (WWDC) 2003 in San Francisco on

Re: [PyKDE] PyQT Segfault on widget removal.

2003-06-18 Thread Vio
Henry Kleynhans wrote: Hi Vio, Thanks for the reply. Would you use deleteLater() instead of removeChild() ? The problem is that it works if the button is not inside another widget which gets removed. If you have the button on the QMainWindow instead of the TestWidget, it works fine, but as

Re: [PyKDE] PyQT Segfault on widget removal.

2003-06-18 Thread Henry Kleynhans
Hi all, Ok, the following seems to work ok. # Don't do this # self.myParent.removeChild(self.myChild) self.myChild.deleteLater() del self.myChild Lemme know if you disagree with this. TA for the help and stuph. Kind regards, Henry On Wednesday 18 June 2003

Re: [PyKDE] PyQT Segfault on widget removal.

2003-06-18 Thread Phil Thompson
On Wednesday 18 June 2003 12:37 pm, Henry Kleynhans wrote: Hi all, Ok, the following seems to work ok. # Don't do this # self.myParent.removeChild(self.myChild) self.myChild.deleteLater() del self.myChild Strictly speaking you don't need the del as it doesn't

Re: [PyKDE] PyQT Segfault on widget removal.

2003-06-18 Thread Henry Kleynhans
Hi Phil, Quick question; if I use the deleteLater() function do I have to delete the local reference to the object, i.e.: self.myWidget.deleteLater() do I have to do: del self.myWidget Kind regards, Henry On Wednesday 18 June 2003 13:37, Henry Kleynhans wrote: Hi all,

Re: [PyKDE] PyQT Segfault on widget removal.

2003-06-18 Thread Henry Kleynhans
Hi Phil, It seems to be a Qt problem. I have some code that illustrates the same in C++. (well, I hope it does...) Kind regards, Henry On Wednesday 18 June 2003 13:27, Phil Thompson wrote: I'll add it to the FAQ, but I don't think it's a PyQt bug - unless anybody wants to do a C++ version