Bug 664 – Cannot emit signal with argument QtMobility.Organizer.QOrganizerTodo

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 664 - Cannot emit signal with argument QtMobility.Organizer.QOrganizerTodo

Summary:

Cannot emit signal with argument QtMobility.Organizer.QOrganizerTodo

Status:	CLOSED DUPLICATE of bug 657

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	HEAD
Platform:	All All

Importance:	P3 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-02-03 18:10 EET by Bruno Araujo
Modified:	2011-02-17 19:19 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Test case (555 bytes, text/x-python) 2011-02-03 18:10 EET, Bruno Araujo	Details
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 Bruno Araujo 2011-02-03 18:10:17 EET

Created attachment 250 [details]
Test case

If a have a signal with QOrganizerTodo as argument, I get a error when emitting
it. The attached example breaks with the following error message:

    $ python testcase.py 
    Error calling slot "emitSignal" 
    Traceback (most recent call last):
      File "testcase.py", line 12, in emitSignal
        self.somethingWasDone.emit(QOrganizerTodo())
    TypeError: Unknown type used to emit a signal: QtMobility::QOrganizerTodo*

The same problem happens if I use QOrganizerItemDetail, a class also in
Organizer module.

Comment 1 Bruno Araujo 2011-02-03 18:15:09 EET

Error message when using QOrganizerItemDetail:

    $ python testcase.py 
    Error calling slot "emitSignal" 
    Traceback (most recent call last):
      File "testcase.py", line 12, in emitSignal
        self.somethingWasDone.emit(QOrganizerItemDetail())
    TypeError: Unknown type used to emit a signal:
QtMobility::QOrganizerItemDetail

Both classes are in QtMobility C++ namespace. Maybe this could be related to
the problem?

Comment 2 Hugo Parente Lima 2011-02-03 18:27:31 EET


*** This bug has been marked as a duplicate of bug 657 ***

Comment 3 Hugo Parente Lima 2011-02-17 19:19:06 EET

Closing bug due to 1.0.0~rc1 release.