[FLAGON-75] Runtime error when QObject is out of scope

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: UserALE.PyQt5 0.1.0
• Fix Version/s: UserALE.PyQt5 0.1.0
• Component/s: UserALE.PyQt5
• Flags: Patch
• Sprint: Sprint 2
• Assignee: Michelle Beard
• Reporter: Michelle Beard
• Due: 23/Sep/16
• Created: 20/Sep/16 14:31
• Updated: 21/Jun/17 20:13
• Resolved: 20/Sep/16 19:50

Description

I just updated and now I’m seeing this:

Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/userale/ale.py", line 216, in aggregate
aggdata = self.__create_msg (event[0], event[1], event[2], details=

{"count" : counter}

)
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/userale/ale.py", line 370, in __create_msg
"target": self.getSelector (object),
File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/userale/ale.py", line 243, in getSelector
return object.objectName () if object.objectName () else object.staticMetaObject.className ()
RuntimeError: wrapped C/C++ object of type QPushButton has been deleted

Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

I haven’t done any debugging, but I figured I’d show it to you in case you’ve seen it before (Mac buddies?). It happened when I clicked a button that should have called a user-defined slot, rather than a PyQt slot, not sure if that’s helpful info.