On 21.02.06 02:02:01, Danny Pansters wrote:
On Tuesday 21 February 2006 00:56, Andreas Pakulat wrote:
Hi,
sorry but I have to ask: What is the status of a new PyKDE snapshot that
works with the recent sip changes? I don't want to put any pressure on
Jim, just a short note of his time
On Tuesday 31 January 2006 11:41 pm, Andreas Pakulat wrote:
Hi,
I tried to use sender() in a slot connected to a signal of a QWidget
derived class, however sender() always returns a QObject instance
instead of the original QWidget-derived one.
Is this by purpose and thus sender() is
On Tuesday 24 January 2006 4:12 pm, Ulrich Berning wrote:
Hi,
SIP (tested with snapshot-20060120) doesn't handle unsigned int
correctly. SIP treats unsigned int the same as signed int and I think,
this is wrong.
While 4294967295 (0x) is a legal unsigned int value (on machines
where
On 21.02.06 15:31:29, Phil Thompson wrote:
On Tuesday 31 January 2006 11:41 pm, Andreas Pakulat wrote:
Hi,
I tried to use sender() in a slot connected to a signal of a QWidget
derived class, however sender() always returns a QObject instance
instead of the original QWidget-derived one.
On Tuesday 21 February 2006 4:14 pm, Andreas Pakulat wrote:
On 21.02.06 15:31:29, Phil Thompson wrote:
On Tuesday 31 January 2006 11:41 pm, Andreas Pakulat wrote:
Hi,
I tried to use sender() in a slot connected to a signal of a QWidget
derived class, however sender() always returns
I'm still having some problems understanding the QT-assistant it seems.
I have a tab widget and need to check what tab is the active one, so I
have tried (among other things):
def doSaveMain(self):
if self.isTabEnabled(self.mainTabWidget * sources):
self.doSaveSources
On 21.02.06 20:16:49, Tina Isaksen wrote:
I'm still having some problems understanding the QT-assistant it seems.
To me it seems you have some problems translating the C++-docs to Python
;-)
I have a tab widget and need to check what tab is the active one, so I have
tried (among other
Hi all,
We're observing some issues with methods such as:
(a)void foo(const QString * = NULL);
(b)void bar(const QString * = 0);
We're using Sip 4.3.2, it appears that Sip doesn't
support (a), PyQt 3.15.1 doesn't use (a) and the
yacc parser that sip uses is confusing NULL for
a C++
On Tuesday 21 February 2006 9:14 pm, Nigel Stewart wrote:
Hi all,
We're observing some issues with methods such as:
(a)void foo(const QString * = NULL);
(b)void bar(const QString * = 0);
We're using Sip 4.3.2, it appears that Sip doesn't
support (a), PyQt 3.15.1 doesn't use (a)
We're observing some issues with methods such as:
(a)void foo(const QString * = NULL);
(b)void bar(const QString * = 0);
So, the lesson seems to be that = 0 is good, = NULL is
to be avoided, when it comes to sip bindings.
And when it comes to C++ according to Stroustrup.
No
Andreas Pakulat wrote:
To me it seems you have some problems translating the C++-docs to Python
;-)
Very much so! I know next to nothing about C++
I have a tab widget and need to check what tab is the active one, so I have
tried (among other things):
What exactly does that mean?
11 matches
Mail list logo
