Bug 818 – QGeoPositionInfo: does not accept QDateTime as timestamp

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 818 - QGeoPositionInfo: does not accept QDateTime as timestamp

Summary:

QGeoPositionInfo: does not accept QDateTime as timestamp

Status:	CLOSED ALREADYFIXED

Product:	PySide Mobility
Classification:	Unclassified
Component:	Location
Version:	0.2.0
Platform:	N900 Maemo5/Fremantle

Importance:	P1 major
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-04-07 22:40 EEST by dom
Modified:	2011-06-22 20:25 EEST (History)
CC List:	8 users (show)

See Also:

Attachments
Code that reproduces the error described. (164 bytes, text/x-python) 2011-04-07 22:40 EEST, dom	Details
unit test (433 bytes, text/x-python) 2011-04-13 17:44 EEST, renato filho	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 dom 2011-04-07 22:40:13 EEST

Created attachment 305 [details]
Code that reproduces the error described.

After upgrading to PySide 1.0.1 the timestamp()-method of QGeoPositionInfo
seems to return a QDate instead of a QDateTime. And the setTimestamp()-method
expects a QDate (instead of QDateTime)

This is the error:
TypeError: 'QtMobility.Location.QGeoPositionInfo.setTimestamp' called with
wrong argument types:
  QtMobility.Location.QGeoPositionInfo.setTimestamp(PySide.QtCore.QDateTime)
Supported signatures:
  QtMobility.Location.QGeoPositionInfo.setTimestamp(PySide.QtCore.QDateTime)

Comment 1 dom 2011-04-08 21:07:04 EEST

Just wanted to mention that this is a regression from 1.0.0 to 1.0.1. It worked
in 1.0.0

Comment 2 renato filho 2011-04-08 22:53:02 EEST

due the regression changing the priority to P1.

Comment 3 renato filho 2011-04-13 17:44:24 EEST

Created attachment 309 [details]
unit test

Comment 4 renato filho 2011-04-13 17:44:50 EEST

works fine on Desktop. I will try test this on device.

Comment 5 Lauro Moura 2011-04-13 17:50:39 EEST

Works for me in a PR 1.3 device with PySide 1.0.1 and python-qtmobility
0.2.0-0maemo1.

Comment 6 renato filho 2011-04-13 17:59:04 EEST

Could you provide more info about your environment?

Which version of pyside, python-qtmobility version are you using? 

This problem happen on scrachbox or on device?

Comment 7 dom 2011-04-13 18:42:30 EEST

I am also running Maemo5 PR1.3 and after the latest upgrade (apt-get update;
apt-get upgrade) to python-pyside 1.0.1-1maemo3 and python-qtmobility
0.2.0-0maemo8 everything works ok. 

Previously I was running:
python-qtmobility 0.2-0maemo7
python-pyside 1.0.1-1maemo1
And with that configuration the problem occurred on the N900. 

Thanks,
Dominik

Comment 8 renato filho 2011-04-13 19:20:02 EEST

Ok then, I will mark this bug as "alreadyfixed" and commit the unit test to
avoid regressions.

Thanks

Comment 9 dom 2011-05-07 18:08:02 EEST

Hi Renato,

can #818 be prevented from reappearing? I know that you said it had something
to do with pyside-qtmobility ...

Comment 10 renato filho 2011-05-08 06:24:19 EEST

Due some problems on fremantle builder the packages is taking so long to build.
I will announce on ML when I get pyside-moibility done.

Comment 11 renato filho 2011-05-10 00:35:37 EEST

pyside-mobility  packages updated.

Comment 12 renato filho 2011-06-22 20:25:19 EEST

release 1.0.4