After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699870 - cooridanate properties changes not notified
cooridanate properties changes not notified
Status: RESOLVED FIXED
Product: libchamplain
Classification: Core
Component: view
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libchamplain-maint
libchamplain-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-07 20:04 UTC by Zeeshan Ali
Modified: 2013-05-07 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Zeeshan Ali 2013-05-07 20:04:24 UTC
It would seem that in git master of libchamplain, updates to "latitude" and "longitude" properties of ChamplainView are not triggering notify signals, at least when view is changed due to user interaction.

FWIW, This is what Maps use for keep tracking of view changes so that if user's location is no longer visible, we can automatically disable the 'track me' button.
Comment 1 Jiri Techet 2013-05-07 22:24:27 UTC
Over the weekend I made some more changes in this area so it should work now. Please test.

Note that you won't be notified every time the latitude/longitude changes during the panning - this would be 60-times per second and people have objected in the past that this is too often (e.g. when you need to draw something based on the change) and slows down the animation. So you'll get only about 3 notifications per second and a notification for the final position.
Comment 2 Zeeshan Ali 2013-05-07 23:16:12 UTC
(In reply to comment #1)
> Over the weekend I made some more changes in this area so it should work now.
> Please test.

Yeah, this works now. I broke somethings on my end in the meantime though. :)

> Note that you won't be notified every time the latitude/longitude changes
> during the panning - this would be 60-times per second and people have objected
> in the past that this is too often (e.g. when you need to draw something based
> on the change) and slows down the animation. So you'll get only about 3
> notifications per second and a notification for the final position.

Its fine. I really don't need a lot of granularity here.