aboutsummaryrefslogtreecommitdiff
path: root/docs/reference/libmm-glib
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2019-10-25 13:27:39 +0200
committerAleksander Morgado <aleksander@aleksander.es>2019-10-27 16:30:37 +0100
commitd09aa38552606e175fcda92a12efec5b9d8f5bc8 (patch)
treec66bcf67479f6bc2bb204812d5c8973f533ce118 /docs/reference/libmm-glib
parentf9ea0c1d9cfe6b57a556060b7d9374a64457d183 (diff)
libmm-glib,location: fix 'unknown' lat/long/alt numeric values
G_MINDOUBLE is 0.0, which is a valid altitude, latitude, and longitude. Change the 'unknown' location values to -G_MAXDOUBLE instead, which is a completely invalid value in all cases. This is strictly an ABI break, but it's also true that until now the methods returning these 'unknown' values could also return valid 0.0 values that would have been detected as 'unknown' by the caller. So, just stop this madness and don't consider this any ABI break. This is the same thing we had to do with MM_SIGNAL_UNKNOWN in fe66bdf65e57fa7dee3dcb8dea068fb3fc7aec34.
Diffstat (limited to 'docs/reference/libmm-glib')
0 files changed, 0 insertions, 0 deletions