Bug 669 – PySide Example shows weird behaviour in QtGui.QPixmap

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 669 - PySide Example shows weird behaviour in QtGui.QPixmap

Summary:

PySide Example shows weird behaviour in QtGui.QPixmap

Status:	CLOSED INVALID

Product:	PySide
Classification:	Unclassified
Component:	QtGui
Version:	1.0.0 beta5
Platform:	All All

Importance:	P3 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-02-07 12:02 EET by Markus Ullmann
Modified:	2011-03-04 15:10 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Markus Ullmann 2011-02-07 12:02:04 EET

Relevant Traceback:

$ python draggableicons.py
Traceback (most recent call last):
  File "draggableicons.py", line 102, in mousePressEvent
    dataStream << pixmap << QtCore.QPoint(event.pos() - child.pos())
TypeError: 'PySide.QtGui.QPixmap.__lshift__' called with wrong argument types:
  PySide.QtGui.QPixmap.__lshift__(PySide.QtCore.QPoint)
Supported signatures:
  PySide.QtGui.QPixmap.__lshift__(PySide.QtCore.QDataStream)

Reproducable:
Swap icons multiple times from left to right and back again

Comment 1 Hugo Parente Lima 2011-02-08 13:35:32 EET

Sorry, but I could not reproduce the bug. Can you provide more info about how
to reproduce the bug?

Comment 2 Hugo Parente Lima 2011-02-16 14:46:59 EET

I still unable to reproduce the bug, I tried again and looked at the Python
code around the speficied line to check for problems but nothing, the line is
executed but without this exception.

If you have any recipe to reproduce the bug please comment here, otherwise I'll
need to change the status to invalid.

Comment 3 Hugo Parente Lima 2011-02-21 15:49:40 EET

Closing the bug as invalid after trying to reproduce it twice without success
and wait a week for some more info without answer.

You can reopen the bug if you have some detailed info about how to reproduce
the bug.

Thanks.

Comment 4 Hugo Parente Lima 2011-03-04 15:10:42 EET

Closing bug due to 1.0.0 release.