-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have no idea how you got tmake involved--it's no longer used. qmake is
what is used with Qt 3. I'd rebuild.
Timothy Grant wrote:
| Thanks for the quick reply.
|
| qt-mac-free-3.3.3.tar.bz2
|
| I think I followed the build instructions correctly as it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What version of Qt are you using? I think tmake is obsolete. See
www.trolltech.com for build instructions.
Timothy Grant wrote:
| ...That is probably off-topic, but I'm going to ask here anyway.
|
| When I try and build sip on OS/X I get the following e
...That is probably off-topic, but I'm going to ask here anyway.
When I try and build sip on OS/X I get the following error.
Error: This version of Qt seems to use tmake but the TMAKEPATH environment is
not set.
My search has turned up all sorts of possible ways to set this, but
none of them see
> Fredrik Juhlin wrote:
> > From what we can tell though, it only happens to widgets that comes from
> > "C++ land", so to speak. That is, widgets that are created by
> > QWidgetFactory, the listbox you get when calling QComboBox.listBox(),
> > the header from QListView.header() etc. This has m
When I am debugging, and an unhandled exception occurs, eric offers me a
dialog which can be dismissed with "Continue", and "Break". I cannot tell
what the difference is between these choices.
I would have expected that "break" would preserve the context of the
exception, permitting me to post-
When I use view/split, a new empty split pane appears, but I can get nothing
to appear in that pane: selecting a file in the browser makes it appear in
the original pane.
Without documentation, here is what I would have expected to have happen:
View/split would create a new pane, also showing
If _anyone_
has gotten this to compile into python under MSVC, I would greatly appreciate
hearing from you. I am getting desperate.
Thank you.
__
This electronic message may contain proprie
> Hi,
>
> We're having some difficult-to-reproduce problems with SIP/PyQt. At times,
> widgets don't have their right class, i.e. a widget we know to be a
> QLabel,
> QHeader etc. is instead just a QWidget, which of course breaks code that
> tries to access for instance QLabel methods.
>
> From wha
Hi,
We're having some difficult-to-reproduce problems with SIP/PyQt. At times,
widgets don't have their right class, i.e. a widget we know to be a QLabel,
QHeader etc. is instead just a QWidget, which of course breaks code that
tries to access for instance QLabel methods.
From what we can tell
