thanks for the offer stefan, but i have an installer already and i plan on making it available once it gets some testing.
a made a module to abstract the python qt bindings (combined a few that i found online), this module attempts to remove any need for different syntax. that code is available now on the github page. also you might have an old copy of my plugin because there is a fourth example. its called ExampleUIFile and this is where i am still having toruble. i am trying to make it work properly with the abstraction module but with some issues. as far as the QMenu is concerned that looks like you used the wrong arguments. my code works without modification... menu.exec_(QCursor.pos()) from what i know, it is legal to provide a link to the precompiled installer. i think improved documentation is in order, feel free to fork the repro and make changes to the readme.creole then send me a pull request. s On Wed, May 15, 2013 at 6:30 AM, Stefan Kubicek <[email protected]>wrote: > Hi Steven, > > I managed to compile and create a Windows installer for PySide 1.1.3 using > Qt 4.8.4, VS2010 and Python 2.7.4, all x64. For a quick test I also > modified the PyQtForSoftimage Python scripts to use the PySide libs instead > of PyQt and I was able to run the ExampleDialog and ExampleSignalSlot > Examples that come with your addon. > The ExampleMenu example throws an error when clicking on one of the menu > items from the popup, it looks like PySide expects a slightly different > syntax, which should be fixable: > > TypeError: 'PySide.QtGui.QMenu.exec_' called with wrong argument types: > # PySide.QtGui.QMenu.exec_(int, int) > # Supported signatures: > # PySide.QtGui.QMenu.exec_() > # PySide.QtGui.QMenu.exec_(list, PySide.QtCore.QPoint, > PySide.QtGui.QAction = None) > # PySide.QtGui.QMenu.exec_(list, PySide.QtCore.QPoint, > PySide.QtGui.QAction, PySide.QtGui.QWidget) > # PySide.QtGui.QMenu.exec_(**PySide.QtCore.QPoint, PySide.QtGui.QAction > = None) > > Besides that it's looking good. > > How far did you get, and is there anything else to consider? > > Also, I don't want to rush ahead, but if it's of any use to you or any one > else (and legal, I suppose?) I can put that installer (or just > shiboken.pyd) and maybe even the modified Plugin scripts up for download > for people to experiment with in the mean time. > I also thought of documenting the build process (also as a reminder for me > should I ever have to do this again), since most of the info is scattered > all over the net and there are likely others who need to compile themselves > too at some point and could save a lot of time with all info in one place. > Let me know what you think.from
