Hello Renato,


Thanks for your patch I will check this ASAP, now I working to get
some critical bugs fixes before the next release.



Thanks for considering the patch.

Take your time. I will watch this thread for updates from the PySide team.


I could not find a way to compile PySide with a custom workspace (aka
QT_NAMESPACE) so I submit this patch.

If there is a way please let me know how, otherwise I hope you can
incorporate this.


Changes summary:

1. I injected the FromCObject() method to QWidget(). This allows passing
widgets wrapped in a CObject from a C++ program.

I think this is a good functionality but this should be more generic
and create a global function to works with any PySide type, will be
strange have this only for QWidget.


Yes you are right. Perhaps the Shiboken API allows passing C++ objects wrapped PyCObjects to PySide, perhaps not, no idea.

In PyQt, sip module allows that:

py_qwidget = sip.wrapinstance(sip.voidptr(pycobj_cpp_qwidget).__int__(), QtGui.QWidget)


2. To specify the namespace just set QT_NAMESPACE environment variable
to the desired value before calling CMake.

Now that is not optimal but I am a newbie at CMake
I will check this and verify if we have a best solution for that


Thanks.


3. In shiboken, this:

[quote]
//only cause namespace confusion
enum SampleNamespace

[/quote]

Is not compiling with VC 9, I commented it out. You can ignore this
patch nonetheless can you verify that VC 9 fails to build during its
presence?

Yes I know that, and we have already fixed that to windows on git head.


Excellent.

Btw, is there is a way to exclude building the tests, phonon and other select stuff while configuring / building PySide? Currently I comment out the targets from the cmake files.

Regards,
Elias

_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside

Reply via email to