On Tue, Jul 28, 2009 at 3:53 PM, Phil Thompson <span dir="ltr"><<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 28 Jul 2009 15:38:09 +0200, Arve Knudsen <<a href="mailto:arve.knudsen@gmail.com" target="_blank">arve.knudsen@gmail.com</a>><br>
wrote:<br>
<div><div></div><div>> Hi<br>
><br>
> Are there any good troubleshooting techniques when unable to get a type<br>
> definition from the SIP API? Sometimes, when there are inconsistencies in<br>
> my<br>
> build I am unable to get the type definition for QWidget, and I waste a<br>
lot<br>
> of time trying to find out what's gone wrong. If SIP itself could give me<br>
> some useful info wrt. to its state, I'm sure that could save me a great<br>
> deal<br>
> of time.<br>
<br>
</div></div>I don't know what you mean by its state.<br>
<br>
QWidget's type definition is a static data structure - sipType_QWidget. You<br>
don't get it, you just reference it.<font color="#888888"></font></blockquote><div><br>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? What I do is call api_find_type("QWidget"), which in this case returns NULL.<br>
<br>Arve<br></div></div>