Andreas Ekoutsidis

Greken

About Me

EXPERTISE
Developer
INDUSTRY
Film/TV

Connect

LOCATION
Sweden
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

No stacktrace from errors triggered in Qt5 applications in Houdini 16 May 22, 2017, 10:05 a.m.

Hi,

I have noticed that since the move from Qt4 to Qt5 I can no longer see the stacktrace from an error if it occurred in a currently running Qt dialog within Houdini 16. I have noticed the same for Maya 2016, but at least there you can see the error if you run:

import traceback
traceback.print_stack()

How do you achieve this in Houdini 16? Running the above commands will only reveal an issue in houdiniInterpreter which I guess is the middle man? The Qt dialogs are executed from the main menu.


Thanks in advance,
Andreas

H12.5: PyQt4 (thread safe) + MySQLdb (not thread safe) Aug. 26, 2013, 8:10 a.m.

By using PyQt4's provided QtSql module I was able to skip the MySQLdb module and therefor solved my issue! The only thing that wasn't clear was that the MySQL driver "QMYSQL" you need to supply for the QtSql module is not a part of the default installation.

My first thought was that I had to recompile PyQt4 but it turned out that I only had to install the qt-mysql package on my machine using the OS's package system

H12.5: PyQt4 (thread safe) + MySQLdb (not thread safe) Aug. 23, 2013, 11:12 a.m.

Yeah that was my first attempt. MySQLdb didn't like it at all.

Right now I'm trying out another approach using PyQt4's SQL module but I just came to realize that the “QMYSQL” driver was not installed by default when I compiled PyQt4 so I'm going to redo that process and try to make it work. Will post my results here when I'm done!