Anupam Basaktext not yet in the index
https://doc.qt.io/qtforpython/shiboken6/shibokenmodule.html#wrapInstance sounds like it would do this
Freyahttps://doc.qt.io/qtforpython/shiboken6/shibokenmodule.html#wrapInstance sounds like it would do this
Question : what would type argument look like here for QObject?
Anupam BasakQuestion : what would type argument look like here for QObject?
I'm guessing you would pass QObject, but I haven't tried
Anupam BasakQuestion : what would type argument look like here for QObject?
Yep, just pass QObject - as it's imported from QtCore.
Stefan de KoninkAre there things not exposed in PySide on purpose? For example, I cannot find QAnimationDriver, while it is part of QtCore.
On the wiki somewhere there is a list of missing things - usually it's due to templated arguments. I don't think I recall QAnimationDriver being on that list though.
@cmaureir has posted it on here before. Let me see if I can find it.
@Keithel trying to solve it now with a Shiboken binding, for the C++ code that I wanted to do a more native python implemantion for.
id 835851715Ссылка
I just listened to a Talk Python To Me podcast episode on this. It sounds interesting, but different from PySide2/6.
>>> from PyMovieRenderer import *
Program received signal SIGSEGV, Segmentation fault.
init_MovieRenderer (module=<module at remote 0x7fffe3dc76f0>) at /home/skinkie/Sources/py_qml_movie_renderer/PyMovieRenderer/movierenderer_wrapper.cpp:886
Which boils down to;
886 _Sbk_MovieRenderer_Type = Shiboken::ObjectType::introduceWrapperType(
887 module,
888 "MovieRenderer",
889 "MovieRenderer*",
890 &Sbk_MovieRenderer_spec,
891 &Shiboken::callCppDestructor< ::MovieRenderer >,
892 reinterpret_cast<SbkObjectType *>(SbkPySide2_QtCoreTypes[SBK_QOBJECT_IDX]),
893 0,
894 0 );
Stefan de Konink@Keithel it is basically required for offscreen rendering.
qi see it now. It's not documented, but I see it's a public class.
No documentation:
https://doc.qt.io/qt-6/animation-overview.html#classes-in-the-animation-framework
But, public:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/animation/qabstractanimation.h?h=6.2.3#n142
hi, is it possible to "keep alive" QtObject properties from dynamic created windows? I store a QtObject in a property in the new window, and store a reference to the created window in a list in the parent window, however, if I create another window after the first one (without exiting the first window), I can't access the QtObject in the first window anymore, I get null when accessing it.