[maya] Maya2013 and QTableView broken?

Coding
1

So I released my Digital Pose Test app for Maya2013. It makes heavy use of pyqt’s QTableView. When a user clicks a cell in the table, the signal ‘clicked(QModelIndex)’ gets fired. This works fine in Maya2012. But in Maya2013 it makes Maya crash.

I tried the ‘pressed(QModelIndex)’ signal as well - same thing.

Has anyone else experienced this yet?

2

[QUOTE=cgjedi;17535]So I released my Digital Pose Test app for Maya2013. It makes heavy use of pyqt’s QTableView. When a user clicks a cell in the table, the signal ‘clicked(QModelIndex)’ gets fired. This works fine in Maya2012. But in Maya2013 it makes Maya crash.

I tried the ‘pressed(QModelIndex)’ signal as well - same thing.

Has anyone else experienced this yet?[/QUOTE]

I’ve had issues in 2013 with model/view ui’s that internally used QModelIndex.internalPointer() This has caused crashes for me. Simply storing the data internally and accessing manually got over the problems for me. It may not be your problem in this instance tho.

Hope this may help.

Dave

3

Oddly enough, I ran into the crashing-when-click-fired in Maya2012 when using a QListView.

I worked around it by firing based on the selection model under the view changing, instead of the view being clicked:


self.yourListView.selectionModel().selectionChanged.connect(self.yourSelectionChangedFunction)

Phil

4

Thanks for the suggestions. I have a support request into Autodesk. I’ll see what they say.

5

are you using a proxy model in between the view and the data model? i remember having some nasty python crashes when not mapping to source correctly.

6

My code is nothing crazy at all. The issue is what works in Maya2012 no longer does with Maya2013. Still waiting for my Autodesk ticket to even be assigned to someone…

7

So…silly me. The answer is that I forgot Maya 2013 uses Visual Studio 2010. My Qt and PyQt are still the compiled ones for Maya2012. Even though they seem to “work” on the surface, it’s really not the case. The question is if anyone has made available VS2010 compiled versions (before I do it myself)?

8

Did using VS2010 compiled versions solve your issue? And if so could you possibly make your compiled versions available ?