Re: [PyKDE] Re: Kcontrol modules.

2003-07-09 Thread Jim Bublitz
On Wednesday July 9 2003 15:20, David Boddie wrote: > Following up to this again as things change... > > On Tue, 8 Jul 2003 20:21:21, Simon Edwards <[EMAIL PROTECTED]> wrote: > > I had a look at the IOSlave code and saw that it works quite > > differently than kcms. Kcms are basically shared libra

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Jonathan Gardner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 09 July 2003 18:46, Steve Simmons wrote: > On Wed, Jul 09, 2003 at 02:14:33PM -0700, Jonathan Gardner wrote: > > On Wednesday 09 July 2003 13:32, Steve Simmons wrote: > > > On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote: > > > I

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Steve Simmons
On Wed, Jul 09, 2003 at 02:14:33PM -0700, Jonathan Gardner wrote: > On Wednesday 09 July 2003 13:32, Steve Simmons wrote: > > On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote: > > I would normally do 'python build.py' and 'make' as an ordinary > > user, then 'make install' as root. Unfo

[PyKDE] Re: Kcontrol modules.

2003-07-09 Thread David Boddie
Following up to this again as things change... On Tue, 8 Jul 2003 20:21:21, Simon Edwards <[EMAIL PROTECTED]> wrote: > I had a look at the IOSlave code and saw that it works quite differently > than kcms. Kcms are basically shared libraries that have a factory method > that returns a instances of

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Jonathan Gardner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 09 July 2003 13:32, Steve Simmons wrote: > On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote: > > These issues have been resolved. I'm just noting them here in case > > anyone else has the same problem. Not sure how they would si

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Steve Simmons
On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote: > These issues have been resolved. I'm just noting them here in case anyone > else has the same problem. Not sure how they would since it was my > own idiocy...but I can't be the only one this unobservant, can I? Nope, I did it too. I

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Rob Knapp
These issues have been resolved. I'm just noting them here in case anyone else has the same problem. Not sure how they would since it was my own idiocy...but I can't be the only one this unobservant, can I? The whole problem was that I wasn't watching the make processes for errors. Apparently

Re: Re[2]: [PyKDE] Problems compiling PyQt 3.7

2003-07-09 Thread Jonathan Gardner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 09 July 2003 06:00, mazu wrote: > Witaj Hans-Peter, > > W Twoim liœcie datowanym 8 lipca 2003 (21:56:03) mo¿na przeczytaæ: > > HPJ> Your env. is missing the qt3-devel package. > > HPJ> Pete > > >> I get errors about QAssistantClient whil

[PyKDE] Re: Kcontrol modules

2003-07-09 Thread David Boddie
On Tue, 8 Jul 2003 20:21:21, Simon Edwards <[EMAIL PROTECTED]> wrote: > Anyone here tried doing kcontrol modules in Python+PyKDE? Not yet. > After seeing the success of IOSlaves in Python, I would like to be able to > kcontrol modules (kcm). I've been playing a bit with coding some admin > progs

Fwd: Re: [PyKDE] Losing Timers

2003-07-09 Thread Phil Thompson
I meant to say, "put the following in (for example) qglobal.sip". Phil--- Begin Message --- On Wednesday 09 July 2003 3:06 pm, Miller, Douglas wrote: > A problem of losing Timer Events on the Qt interest email archive was > solved this way. > > Set 'qt_win_use_simple_timers' in qapplication_win.cp

Re: [PyKDE] Losing Timers

2003-07-09 Thread Phil Thompson
On Wednesday 09 July 2003 3:06 pm, Miller, Douglas wrote: > A problem of losing Timer Events on the Qt interest email archive was > solved this way. > > Set 'qt_win_use_simple_timers' in qapplication_win.cpp to true. > > The following snippet of code solved it: > > Q_EXPORT extern bool qt_win_use_s

Re: [PyKDE] More 3.7 compile issues

2003-07-09 Thread Phil Thompson
On Wednesday 09 July 2003 4:29 pm, Rob Knapp wrote: > I'm currently compiling on a win32 platform and the build process reported > that sipBadLengthForSlice was an unknown identifier. The line number > provided was line 130 in spi/qstringlist.sip. Make sure you are using SIP v3.7. > For the time

[PyKDE] More 3.7 compile issues

2003-07-09 Thread Rob Knapp
I'm currently compiling on a win32 platform and the build process reported that sipBadLengthForSlice was an unknown identifier. The line number provided was line 130 in spi/qstringlist.sip. For the time being I've hacked the .sip file to simply return NULL in those circumstances since my immedi

[PyKDE] Losing Timers

2003-07-09 Thread Miller, Douglas
A problem of losing Timer Events on the Qt interest email archive was solved this way. Set 'qt_win_use_simple_timers' in qapplication_win.cpp to true. The following snippet of code solved it: Q_EXPORT extern bool qt_win_use_simple_timers; void someInitFunction() { ... qt_win_use_simple

Re[2]: [PyKDE] Problems compiling PyQt 3.7

2003-07-09 Thread mazu
Witaj Hans-Peter, W Twoim liœcie datowanym 8 lipca 2003 (21:56:03) mo¿na przeczytaæ: HPJ> Your env. is missing the qt3-devel package. HPJ> Pete >> >> I get errors about QAssistantClient while compiling PyQt 3.7, on my >> debian woody with Qt 3.1.2. Here is compiler message: Could you tell

Re: [PyKDE] SIP: wrapper code calls virtual functions with base class prefix

2003-07-09 Thread Phil Thompson
On Tuesday 08 July 2003 12:49 pm, Tore Knabe wrote: > Hi, > > I want to wrap a base class, which serves as an > interface, and inherit from this base class in C++. > The C++ class, which is not wrapped, overrides the > virtual function foo() from the base class. My > problem: when I call a factory