PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 425 - RuntimeError while passing event to slider
: RuntimeError while passing event to slider
Status: CLOSED WORKSFORME
Product: PySide
Classification: Unclassified
Component: QtGui
: HEAD
: PC Linux
: P3 normal
Assigned To: Hugo Parente Lima
:
:
:
  Show dependency treegraph
 
Reported: 2010-10-21 06:16 EEST by genjix
Modified: 2011-01-06 16:25 EET (History)
8 users (show)

See Also:


Attachments
works for me™ (832 bytes, text/plain)
2010-12-28 11:59 EET, Hugo Parente Lima
Details

Note You need to log in before you can comment on or make changes to this bug.
Description genjix 2010-10-21 06:16:20 EEST
I am catching a scroll wheel event and passing it to a slider:


    def wheelEvent(self, event):
        pos = QtCore.QPoint(0,0)
        event = QtGui.QWheelEvent(pos, event.delta(), event.buttons(),
event.modifiers(), event.orientation())
        QtGui.QApplication.sendEvent(self.slider, event)

For the most part it works well. But if the slider is at the ends- 0 or 100,
then continuing scrolling produces this error:


Original exception was:
Traceback (most recent call last):
  File "main.py", line 140, in wheelEvent
    pos = QtCore.QPoint(0,0)
RuntimeError: maximum recursion depth exceeded while calling a Python object
Traceback (most recent call last):
  File "main.py", line 140, in wheelEvent
    pos = QtCore.QPoint(0,0)
RuntimeError: maximum recursion depth exceeded while calling a Python object
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 48, in
apport_excepthook
    if not enabled():
  File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 21, in
enabled
    import re
RuntimeError: maximum recursion depth exceeded while calling a Python object
Comment 1 Matti Airas 2010-11-23 05:56:35 EET
I'm acknowledging the bug and retaining P3. This will be fixed hopefully during
the next sprint (since it's been around for a while already).
Comment 2 Hugo Parente Lima 2010-12-28 11:59:00 EET
Created attachment 206 [details]
works for me™

I did a small test here and it worked.

You need to provide some code snippet otherwise will be impossible to me to
guess what's going wrong.

Marking the bug as WORKSFORME and also attaching a example showing it working.
Feel free to reopen the bug if it still valid for you but don't forget to
provide some code, so I can test it.
Comment 3 renato filho 2011-01-06 16:25:20 EET
released on beta3