On Tue, Jul 28, 2009 at 4:12 PM, Phil Thompson <[email protected]>wrote:
> On Tue, 28 Jul 2009 16:03:05 +0200, Arve Knudsen <[email protected]> > wrote: > > On Tue, Jul 28, 2009 at 3:53 PM, Phil Thompson > > <[email protected]>wrote: > > > >> On Tue, 28 Jul 2009 15:38:09 +0200, Arve Knudsen > <[email protected]> > >> wrote: > >> > Hi > >> > > >> > Are there any good troubleshooting techniques when unable to get a > type > >> > definition from the SIP API? Sometimes, when there are inconsistencies > >> > in > >> > my > >> > build I am unable to get the type definition for QWidget, and I waste > a > >> lot > >> > of time trying to find out what's gone wrong. If SIP itself could give > >> > me > >> > some useful info wrt. to its state, I'm sure that could save me a > great > >> > deal > >> > of time. > >> > >> I don't know what you mean by its state. > >> > >> QWidget's type definition is a static data structure - sipType_QWidget. > >> You > >> don't get it, you just reference it. > > > > > > This is from an application embedding Python, so I'm calling SIP's C API. > > In this case I have no choice but to go via the API right? > > Right. > > > What I do is > > call > > api_find_type("QWidget"), which in this case returns NULL. > > I would think the most likely thing in that case is that the QtGui module > hasn't been imported. It has been imported, and like I said this code works for certain builds. It is indicative of inconsistent builds that it doesn't work, and it would be great to have some debugging aids. Arve
_______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
