Re: [PyKDE] Eric3 source documentation

2006-01-17 Thread jul
Bowen, Brian M wrote: Maybe I didn't ask the right question. I'd like to be able to generate UML diagrams for my own source code. The eric3 web site says that the IDE has the ability, but I am not sure how to use it. Is there documentation on that feature?   Surely I read a bi

RE: [PyKDE] Eric3 source documentation

2006-01-17 Thread Bowen, Brian M
Maybe I didn't ask the right question. I'd like to be able to generate UML diagrams for my own source code. The eric3 web site says that the IDE has the ability, but I am not sure how to use it. Is there documentation on that feature?   Thanks, Brian From: jul [mailto:[EMAIL PROTECTED] Se

Re: [PyKDE] Eric3: Bug and RFE

2006-01-17 Thread Michael Zimmermann
Detlev Offenbach wrote: Furthermore would it be possible to add support for events in the documentation module? Grepping through the code I found references to @signal, @exception(@raise, @throws) and a bunch of other. @event might be usefull to notify that a certain class or method emits certa

Re: [PyKDE] Eric3: Bug and RFE

2006-01-17 Thread Detlev Offenbach
Am Montag, 16. Januar 2006 20:38 schrieb Michael Zimmermann: > Hi Detlev, > > there seems to be a tiny bug in the Projects > show > Code Metrics > functionality. This method does not test the existance of the files > provided by the project tree in eric3. If the file does not exist (e. g. > deleted

Re: [PyKDE] Eric3 source documentation

2006-01-17 Thread jul
Bowen, Brian M wrote: Eric3 source documentation Can someone tell me how use eric3 for source documentation? Is there an additional module that needs to be installed for this feature to be enabled? Just go in the Help section : Help->Eric Documentation This should open the integr

[PyKDE] [pyqt3] QiconView and "memory security violation" or something like this

2006-01-17 Thread piotr maliński
I have a problem with my little script. I've described it on gentoo forums: http://forums.gentoo.org/viewtopic-p-3033085.html#3033085 I've also rewrote those two functions into one: ### def list_dir(self): import glob import os.path # get patch f

[PyKDE] Eric3 source documentation

2006-01-17 Thread Bowen, Brian M
Title: Eric3 source documentation Can someone tell me how use eric3 for source documentation? Is there an additional module that needs to be installed for this feature to be enabled? Thanks, Brian ___ PyKDE mailing listPyKDE@mats.imk.fraunh

Re: [PyKDE] Segault > Bug in pyQT? (Or stupid me?)

2006-01-17 Thread Michael Zimmermann
Phil Thompson wrote: No, I mean the gdb backtrace. Sorry! First time I used gdb so far here we go: #0 0x080885e2 in _Py_ForgetReference (op=0xb61131ec) at Objects/object.c:1847 #1 0x08088655 in _Py_Dealloc (op=0xb61131ec) at Objects/object.c:1868 #2 0x081271db in meth_dealloc (m=0xb5c

Re: [PyKDE] Segault > Bug in pyQT? (Or stupid me?)

2006-01-17 Thread Phil Thompson
On Tuesday 17 January 2006 3:44 pm, Michael Zimmermann wrote: > Phil Thompson wrote: > > Hi Phil, > > > At the very least you need to post the backtrace, ie. the call stack at > > the point of the segfault. > > well, with backtrace you mean the python backtrace, I guess. I would > have sent it if t

Re: [PyKDE] Segault > Bug in pyQT? (Or stupid me?)

2006-01-17 Thread Michael Zimmermann
Phil Thompson wrote: Hi Phil, At the very least you need to post the backtrace, ie. the call stack at the point of the segfault. well, with backtrace you mean the python backtrace, I guess. I would have sent it if there actually would be one. What I get is as follows (the debug messages ar

Re: [PyKDE] Segault > Bug in pyQT? (Or stupid me?)

2006-01-17 Thread Phil Thompson
On Tuesday 17 January 2006 3:09 pm, Michael Zimmermann wrote: > Hi there, > > in a multithreaded application we are currently struggling with > segfaults at application exit. The segfaults occur after the > qApp.exec_loop() finishes. Below is the gdb trace done with a complete > debug environment.

[PyKDE] Segault > Bug in pyQT? (Or stupid me?)

2006-01-17 Thread Michael Zimmermann
Hi there, in a multithreaded application we are currently struggling with segfaults at application exit. The segfaults occur after the qApp.exec_loop() finishes. Below is the gdb trace done with a complete debug environment. In the application threads (subclassed from QThread; no python thre