Bug 534 – [Maemo5] Error conncecting QGeoPositionInfoSource.positionUpdated signal

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 534 - [Maemo5] Error conncecting QGeoPositionInfoSource.positionUpdated signal

Summary:

[Maemo5] Error conncecting QGeoPositionInfoSource.positionUpdated signal

Status:	CLOSED DUPLICATE of bug 528

Product:	PySide Mobility
Classification:	Unclassified
Component:	Location
Version:	0.1.0
Platform:	All All

Importance:	P3 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-12-07 12:40 EET by Luca Donaggio
Modified:	2011-01-21 15:44 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 Luca Donaggio 2010-12-07 12:40:49 EET

PySide version: 1.0.0~beta1-maemo4
PySide Mobility version: 0.2-0maemo6

This code snippet:

mypossrc = QGeoPositionInfoSource.createDefaultSource(self)
if mypossrc != None:
  
mypossrc.setPreferredPositioningMethods(QGeoPositionInfoSource.SatellitePositioningMethods) 
  
mypossrc.positionUpdated[QGeoPositionInfo].connect(self.on_gps_position_updated)
# Tried also this one, the result remains the same
#mypossrc.positionUpdated.connect(self.on_gps_position_updated)
   mypossrc.updateTimeout.connect(self.on_gps_update_timeout)


@Slot(QGeoPositionInfo)
def on_gps_position_updated(self,currpos = QGeoPositionInfo()):
   pass

gives this error:

X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 42 (X_SetInputFocus)
  Resource id:  0x3a0000d
Invalid Signal signature: positionUpdated(QtMobility::QGeoPositionInfo)

Comment 1 Matti Airas 2010-12-07 18:51:59 EET

Hi Luca,

thanks for the bug - this indeed is an embarrassing issue which we try to fix
without further delay. However, it's already been reported, so I'm resolving
this bug as duplicate.

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

Comment 2 Luca Donaggio 2010-12-10 07:32:29 EET

Sorry for the noise then :) !
I should definetly learn to check for existing bugs first!

Comment 3 Matti Airas 2010-12-10 08:06:02 EET

(In reply to comment #2)
> Sorry for the noise then :) !
> I should definetly learn to check for existing bugs first!

Don't worry - it takes almost no time for us to identify duplicates, and we
much rather receive a few extra bugs than miss a single one.

Comment 4 renato filho 2011-01-21 15:44:42 EET

release beta4