Re: [PyKDE] Embedded python

2004-05-28 Thread Myddrin
Is libqtc compilied against the same version of QT as you're app is compiled with. I had a similar problem when I was importing a libqtc compiled against qt 3.1.2, but my main app was a qt 3.3.2 app. Just a thought. On Friday 28 May 2004 5:14 pm, Kevin Schmidt wrote: > I am running a QT C++ ap

Re: [PyKDE] Minimizing libqtc's size

2003-12-17 Thread Myddrin
On Wednesday 17 December 2003 5:16 am, Ulrich Berning wrote: > But what is your problem with a module size of 4 megabytes in an > environment where installations or patches always have hundreds of > megabytes. Thanks for the advice I will check into using 3.9 and see how much that saves. The re

[PyKDE] Minimizing libqtc's size

2003-12-16 Thread Myddrin
Has anyone done any work on decreasing the size of libqtc? We are using pyqt 3.7, and libqtc is almost 4 megs. (about 900K when we get done compressing it for re-distribution. Is anyone aware of ways to decrease the size? (Already using -O1 when compiliing.) (This is on windows, btw) _

Re: [PyKDE] Fatal Python error: PyEval_RestoreThread: NULL tstate

2003-12-11 Thread Myddrin
On Wednesday 10 December 2003 5:24 pm, Patrick Stinson wrote: > In coding an audio library that requires the use of different threads > (audio streaming, disk buffering, application), I've run into similar > unexplainable (to me) fatal python errors involving the useage of the C > Python API. the p

[PyKDE] Profiling QThreads

2003-12-05 Thread Myddrin
I'm currently trying to do some fine tuning on an application that has several worker threads. When I use the python profiler (profile.py) to try and breakdown my CPU usage, I'm not getting any feedback regarding my QThreads. Does any know of a tool that will give me this feed back? This is with

Re: [PyKDE] Notifying self on all emits _OR_ overriding default emit behavior

2003-10-06 Thread Myddrin
On Thursday 02 October 2003 15:32, Sundance wrote: > I heard Myddrin said: > > No, I mispoke. Slots should be signals above. > > Oh! I see. :) > > > I would need to take a generic (or ones that inherit from say > > MydWidget) object X and discover it's signals

Re: [PyKDE] Notifying self on all emits _OR_ overriding default emit behavior

2003-10-02 Thread Myddrin
On Thursday 02 October 2003 12:25, Sundance wrote: > I heard Myddrin said: > > If I could discover the slots at run time that would work, yes. > > However PyQT doesn't expose this info (as far as I know) like the QT > > library does.. > > Erm, so you mean you w

Re: [PyKDE] Notifying self on all emits _OR_ overriding default emit behavior

2003-10-02 Thread Myddrin
On Thursday 02 October 2003 09:51, Sundance wrote: > I heard Myddrin said: > > For the sake of argument, let's say I need to know whenever an object > > emits a signal. > > Well... I'm propably gonna say something stupid, but isn't the > straightfoward

[PyKDE] Notifying self on all emits _OR_ overriding default emit behavior

2003-10-01 Thread Myddrin
For the sake of argument, let's say I need to know whenever an object emits a signal. Now, I can hard code each object in my program and do this: self.I_M_ABOUT_TO_EMIT_SOMETHING(PYSIGNAL("PAH"), (snorg, do, flooo) ) emit(SIGNAL("PAH"), (snorg, do, flooo) ) But I'd really rather find some kind