Looking at the manual, it does say: "to use PyQt with NUKE, download the NUKE specific Qt 4.7.2 source code from http://thefoundry.s3.amazonaws.com/products/nuke/developers/70/nuke-qt-4.7.2-src.tar.gz. Run the build.py script with the arguments “release 64” to build all of the binaries (shared libraries and executables) needed to link PyQt." I'll see if the systems people can get it installed for me, but thanks for pointing me in (hopefully) the right direction.
On Mon, Sep 30, 2013 at 8:53 PM, Nathan Rusch <nathan_ru...@hotmail.com> wrote: > Well, if you're seeing inconsistent behavior between Nuke versions, that's > where I would start, since you say it appears to be PyQt-related, and that's > one of the obvious changes that could affect compatibility. I've gotten away > with using mismatched PyQt and Qt builds in the past, but I've also seen > them introduce serious stability problems (particularly on OSX). > > > -Nathan > > > -----Original Message----- From: Jose Fernandez de Castro > Sent: Monday, September 30, 2013 8:47 PM > To: Nuke Python discussion > Subject: Re: [Nuke-python] pyqt panel crashes Nuke 7.0 on close tab (but > notonNuke 6.3) > > > Reusing the same build. Do you think it is a requirement to rebuild > specifically? Might have missed it in the release notes... > > On Mon, Sep 30, 2013 at 8:31 PM, Nathan Rusch <nathan_ru...@hotmail.com> > wrote: >> >> Did you rebuild PyQt against Qt 4.7 for Nuke 7? Or are you just copying or >> otherwise reusing the same build that you've been using for 6.3? >> >> -Nathan >> >> >> -----Original Message----- From: Jose Fernandez de Castro >> Sent: Monday, September 30, 2013 7:43 PM >> To: Nuke Python discussion >> Subject: [Nuke-python] pyqt panel crashes Nuke 7.0 on close tab (but not >> onNuke 6.3) >> >> >> I've seen a bunch of threads here for this type of issue, and I have >> gone through some of the suggested solutions (settings the parent to >> the active window, etc.) but nothing has worked. The strange thing is >> that my panel works fine in 6.3, but crashes when I close it on 7.0 >> (which leads me to believe that it is a pyqt specific issue, and not >> something with my code). Just wondering if anyone has encountered this >> issue moving from one version to the other, and what you've done to >> fix it. My workaround to delete the tab is to float it first, and then >> 'close' the window by clicking on the 'x' button (not the 'close tab' >> command). Unfortunately moving to PySide is not an option at this >> moment... Thanks! >> >> -- >> Jose Fernandez de Castro >> _______________________________________________ >> Nuke-python mailing list >> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> _______________________________________________ >> Nuke-python mailing list >> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > > > > -- > Jose Fernandez de Castro > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- Jose Fernandez de Castro _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
