Documentation/Maemo 5 Developer Guide/Using Connectivity Components/Using Location API - Revision history

amigadave: wiify slightly

2011-03-01T13:42:03Z

wiify slightly

← Older revision		Revision as of 13:42, 1 March 2011
Line 46:		Line 46:
	Here is table that summarizes differences between the methods. Accuracy refers to horizontal accuracy of the fix.		Here is table that summarizes differences between the methods. Accuracy refers to horizontal accuracy of the fix.

-	{\| class="wikitable" ~~style="margin: 1em auto 1em auto"~~	+	{\| class="wikitable"
		+	\|+
		+	Available location methods
		+	\|-
	! Method !! Typical Accuracy !! Requires SIM !! Requires Network !! Drains Battery		! Method !! Typical Accuracy !! Requires SIM !! Requires Network !! Drains Battery
	\|-		\|-
-	\| CWP \|\| ~~1km~~-~~1000km~~ \|\| Yes \|\| No \|\| No	+	\| CWP \|\| 1-1000 km \|\| Yes \|\| No \|\| No
	\|-		\|-
-	\| ACWP \|\| ~~1km~~-~~10km~~ \|\| Yes \|\| Yes \|\| No	+	\| ACWP \|\| 1-10 km \|\| Yes \|\| Yes \|\| No
	\|-		\|-
-	\| GNSS \|\| 5m-100m \|\| No \|\| No \|\| Yes	+	\| GNSS \|\| 5-100m \|\| No \|\| No \|\| Yes
	\|-		\|-
-	\| AGNSS \|\| 5m-100m \|\| Yes \|\| Yes \|\| Yes	+	\| AGNSS \|\| 5-100m \|\| Yes \|\| Yes \|\| Yes
	\|}		\|}

Line 71:		Line 74:

	<code>LocationGPSDevice</code> object has the following public fields:		<code>LocationGPSDevice</code> object has the following public fields:
-	* gboolean online: Whether there is a connection to the hardware	+	* <code>gboolean online</code>: Whether there is a connection to the hardware
	* <code>LocationGPSDeviceStatus status</code>: Status of the device		* <code>LocationGPSDeviceStatus status</code>: Status of the device
	* <code>LocationGPSDeviceFix *fix</code>: The actual fix (latitude, longitude, etc)		* <code>LocationGPSDeviceFix *fix</code>: The actual fix (latitude, longitude, etc)
Line 79:		Line 82:
	* <code>LocationCellInfo *cell_info</code>: Information about cell the device is connected to		* <code>LocationCellInfo *cell_info</code>: Information about cell the device is connected to

-	The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. ''LocationGPSDeviceFix'' fields are listed in table below. In "Fields Flag" column there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set.	+	The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. "<code>LocationGPSDeviceFix</code>" fields are listed in the table below. In "Fields Flag" column there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set.

-	{\| class="wikitable~~" style="margin: 1em auto 1em auto~~"	+	{\| class="wikitable"
	\|+LocationGPSDeviceFix		\|+LocationGPSDeviceFix
	! Variable !! colspan="3" \| Description		! Variable !! colspan="3" \| Description
	\|-		\|-
-	\| mode \|\| colspan="3" \| Mode of the fix (2D, 3D, not seen or no fix)	+	\| <code>mode</code> \|\| colspan="3" \| Mode of the fix (2D, 3D, not seen or no fix)
	\|-		\|-
-	\| fields \|\| colspan="3" \| Bitfield representing what fields contain valid data	+	\| <code>fields</code> \|\| colspan="3" \| Bitfield representing what fields contain valid data
	\|-		\|-
	! Variable !! Unit !! Description !! Fields Flag		! Variable !! Unit !! Description !! Fields Flag
	\|-		\|-
-	\| time \|\| s \|\| Timestamp of the update \|\| <code>LOCATION_GPS_DEVICE_TIME_SET</code>	+	\| <code>time</code> \|\| s \|\| Timestamp of the update \|\| <code>LOCATION_GPS_DEVICE_TIME_SET</code>
	\|-		\|-
-	\| ept \|\| s \|\| Time accuracy	+	\| <code>ept</code> \|\| s \|\| Time accuracy \|\|
	\|-		\|-
-	\| latitude \|\| degrees \|\| Fix latitude \|\| <code>LOCATION_GPS_DEVICE_LATLONG_SET</code>	+	\| <code>latitude</code> \|\| degrees \|\| Fix latitude \|\| <code>LOCATION_GPS_DEVICE_LATLONG_SET</code>
	\|-		\|-
-	\| longitude \|\| degrees \|\| Fix longitude \|\| <code>LOCATION_GPS_DEVICE_LATLONG_SET</code>	+	\| <code>longitude</code> \|\| degrees \|\| Fix longitude \|\| <code>LOCATION_GPS_DEVICE_LATLONG_SET</code>
	\|-		\|-
-	\| eph \|\| cm \|\| Horizontal position accuracy	+	\| <code>eph</code> \|\| cm \|\| Horizontal position accuracy \|\|
	\|-		\|-
-	\| altitude \|\| m \|\| Fix altitude \|\| <code>LOCATION_GPS_DEVICE_ALTITUDE_SET</code>	+	\| <code>altitude</code> \|\| m \|\| Fix altitude \|\| <code>LOCATION_GPS_DEVICE_ALTITUDE_SET</code>
	\|-		\|-
-	\| epv \|\| m \|\| Altitude accuracy	+	\| <code>epv</code> \|\| m \|\| Altitude accuracy \|\|
	\|-		\|-
-	\| track \|\| degrees \|\| Direction of motion \|\| <code>LOCATION_GPS_DEVICE_TRACK_SET</code>	+	\| <code>track</code> \|\| degrees \|\| Direction of motion \|\| <code>LOCATION_GPS_DEVICE_TRACK_SET</code>
	\|-		\|-
-	\| epd \|\| degrees \|\| Track accuracy	+	\| <code>epd</code> \|\| degrees \|\| Track accuracy \|\|
	\|-		\|-
-	\| speed \|\| km/h \|\| Current speed \|\| <code>LOCATION_GPS_DEVICE_SPEED_SET</code>	+	\| <code>speed</code> \|\| km/h \|\| Current speed \|\| <code>LOCATION_GPS_DEVICE_SPEED_SET</code>
	\|-		\|-
-	\| eps \|\| km/h \|\| Speed accuracy	+	\| <code>eps</code> \|\| km/h \|\| Speed accuracy \|\|
	\|-		\|-
-	\| climb \|\| m/s \|\| Current rate of climb \|\| <code>LOCATION_GPS_DEVICE_CLIMB_SET</code>	+	\| <code>climb</code> \|\| m/s \|\| Current rate of climb \|\| <code>LOCATION_GPS_DEVICE_CLIMB_SET</code>
	\|-		\|-
-	\| epc \|\| m/s \|\| Climb accuracy	+	\| <code>epc \|\| m/s \|\| Climb accuracy \|\|
	\|}		\|}

amigadave: add Fremantle link

2010-08-17T12:52:58Z

add Fremantle link

← Older revision		Revision as of 12:52, 17 August 2010
Line 1:		Line 1:
-	Location framework provides a library called liblocation which is used for developing location aware applications in Fremantle. Liblocation supports internal GPS, network based methods and external bluetooth GPS.	+	Location framework provides a library called liblocation which is used for developing location aware applications in [[Open development/Maemo roadmap/Fremantle\|Fremantle]]. Liblocation supports internal GPS, network based methods and external bluetooth GPS.
-		+

	==Using liblocation==		==Using liblocation==

amigadave: use and


2010-08-04T11:13:25Z
use <source> and <code>
Show changes



amigadave: /* Complete example */ fix pkg-config invocation
2010-03-29T15:37:15Z
Complete example:  fix pkg-config invocation

		
		
		
		
		
		
		← Older revision
		Revision as of 15:37, 29 March 2010
		
		Line 246:
Line 246:
  
 You can compile this example with following command:  You can compile this example with following command:
-   gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c +   gcc -Wall `pkg-config --cflags --libs liblocation` -o test test.c
  
 [[Category:Development]]  [[Category:Development]]
 [[Category:Documentation]]  [[Category:Documentation]]
 [[Category:Fremantle]]  [[Category:Fremantle]]




amigadave: categorise
2010-02-12T12:53:33Z
categorise

		
		
		
		
		
		
		← Older revision
		Revision as of 12:53, 12 February 2010
		
		Line 247:
Line 247:
 You can compile this example with following command:  You can compile this example with following command:
   gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c    gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c
  + 
  + [[Category:Development]]
  + [[Category:Documentation]]
  + [[Category:Fremantle]]




jaulio: /* LocationGPSDevice and LocationGPSDeviceFix */
2009-12-03T14:22:59Z
LocationGPSDevice and LocationGPSDeviceFix

		
		
		
		
		
		
		← Older revision
		Revision as of 14:22, 3 December 2009
		
		Line 69:
Line 69:
  
  
- The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. ''LocationGPSDeviceFix'' fields are listed below. In parenthesis there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set. + The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. ''LocationGPSDeviceFix'' fields are listed in table below. In "Fields Flag" column there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set.
  
  + {| class="wikitable" style="margin: 1em auto 1em auto"
  + |+LocationGPSDeviceFix
  + ! Variable !! colspan="3" | Description
  + |-
  + | mode || colspan="3" | Mode of the fix (2D, 3D, not seen or no fix)
  + |-
  + | fields || colspan="3" | Bitfield representing what fields contain valid data
  + |-
  + ! Variable !! Unit !! Description !! Fields Flag
  + |-
  + | time || s || Timestamp of the update || LOCATION_GPS_DEVICE_TIME_SET
  + |-
  + | ept || s || Time accuracy
  + |-
  + | latitude || degrees || Fix latitude || LOCATION_GPS_DEVICE_LATLONG_SET
  + |-
  + | longitude || degrees || Fix longitude || LOCATION_GPS_DEVICE_LATLONG_SET
  + |-
  + | eph || cm || Horizontal position accuracy
  + |-
  + | altitude || m || Fix altitude || LOCATION_GPS_DEVICE_ALTITUDE_SET
  + |-
  + | epv || m ||  Altitude accuracy
  + |-
  + | track || degrees || Direction of motion || LOCATION_GPS_DEVICE_TRACK_SET
  + |-
  + | epd || degrees || Track accuracy
  + |-
  + | speed || km/h || Current speed || LOCATION_GPS_DEVICE_SPEED_SET
  + |-
  + | eps || km/h || Speed accuracy
  + |-
  + | climb || m/s || Current rate of climb || LOCATION_GPS_DEVICE_CLIMB_SET
  + |-
  + | epc || m/s || Climb accuracy
  + |}
  
- *LocationGPSDeviceMode mode: The mode of the fix + The units for epv, epd, eps and epc might be different in liblocation version 0.99-1 and older.
- *guint32 fields: A bitfield representing what fields contain valid data + 
- *double time: The timestamp of the update (LOCATION_GPS_DEVICE_TIME_SET) + 
- *double ept: Time accuracy + 
- *double latitude: Fix latitude (LOCATION_GPS_DEVICE_LATLONG_SET) + 
- *double longitude: Fix longitude (LOCATION_GPS_DEVICE_LATLONG_SET) + 
- *double eph: Horizontal position accuracy + 
- *double altitude: Fix altitude in meters (LOCATION_GPS_DEVICE_ALTITUDE_SET) + 
- *double epv: Vertical position accuracy + 
- *double track: Direction of motion in degrees (LOCATION_GPS_DEVICE_TRACK_SET) + 
- *double epd: Track accuracy + 
- *double speed: Current speed in km/h (LOCATION_GPS_DEVICE_SPEED_SET) + 
- *double eps: Speed accuracy + 
- *double climb: Current rate of climb in m/s (LOCATION_GPS_DEVICE_CLIMB_SET) + 
- *double epc: Climb accuracy + 
-   + 
  
 An application receiving a fix cannot know if the fix is a result from location method it requested. Therefore application should study whether fix is accurate enough to satisfy application's needs. This can be done by inspecting "eph" field, which is fix's horizontal accuracy in centimeters. Typical values for horizontal accuracies can be seen in the location methods table. If accuracy is not known, it has a value of NaN.  An application receiving a fix cannot know if the fix is a result from location method it requested. Therefore application should study whether fix is accurate enough to satisfy application's needs. This can be done by inspecting "eph" field, which is fix's horizontal accuracy in centimeters. Typical values for horizontal accuracies can be seen in the location methods table. If accuracy is not known, it has a value of NaN.
-  
  
 ==Liblocation signals and callbacks==  ==Liblocation signals and callbacks==




jaulio: /* Location methods */
2009-12-03T13:22:31Z
Location methods

		
		
		
		
		
		
		← Older revision
		Revision as of 13:22, 3 December 2009
		
		Line 31:
Line 31:
   g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS | LOCATION_METHOD_AGNSS, NULL);    g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS | LOCATION_METHOD_AGNSS, NULL);
  
- ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is any, an error to application is signalled. + ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is not any, an error to application is signalled.
  
 USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.  USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.




quanyisun: /* Location methods */
2009-09-25T12:03:52Z
Location methods

		
		
		
		
		
		
		← Older revision
		Revision as of 12:03, 25 September 2009
		
		Line 46:
Line 46:
 | ACWP || 1km-10km || Yes || Yes || No  | ACWP || 1km-10km || Yes || Yes || No
 |-  |-
- | GNSS || 1m-100m || No	|| No || Yes + | GNSS || 5m-100m || No	|| No || Yes
 |-  |-
- | AGNSS || 1m-100m || Yes || Yes || Yes + | AGNSS || 5m-100m || Yes || Yes || Yes
 |}  |}
  




quanyisun: /* Location methods */
2009-09-25T12:01:38Z
Location methods

		
		
		
		
		
		
		← Older revision
		Revision as of 12:01, 25 September 2009
		
		Line 31:
Line 31:
   g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS | LOCATION_METHOD_AGNSS, NULL);    g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS | LOCATION_METHOD_AGNSS, NULL);
  
- ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there isn't any, an error to application is signalled. + ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is any, an error to application is signalled.
  
 USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.  USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.




jaulio: /* Complete example */
2009-09-24T14:33:52Z
Complete example

		
		
		
		
		
		
		← Older revision
		Revision as of 14:33, 24 September 2009
		
		Line 162:
Line 162:
   #include <location/location-gpsd-control.h>    #include <location/location-gpsd-control.h>
         
-   static void on_error(LocationGPSDControl *control, gpointer data) +   static void on_error(LocationGPSDControl *control, LocationGPSDControlError error, gpointer data)
   {      {  
-   	g_debug("location error... quitting"); +   	g_debug("location error: %d... quitting", error);
   	g_main_loop_quit((GMainLoop *) data);    	g_main_loop_quit((GMainLoop *) data);
   }    }
Line 211:
Line 211:
   		NULL);    		NULL);
         
-   	g_signal_connect(control, "error", G_CALLBACK(on_error), loop); +   	g_signal_connect(control, "error-verbose", G_CALLBACK(on_error), loop);
   	g_signal_connect(device, "changed", G_CALLBACK(on_changed), control);    	g_signal_connect(device, "changed", G_CALLBACK(on_changed), control);
   	g_signal_connect(control, "gpsd-stopped", G_CALLBACK(on_stop), loop);    	g_signal_connect(control, "gpsd-stopped", G_CALLBACK(on_stop), loop);
Line 226:
Line 226:
  
 You can compile this example with following command:  You can compile this example with following command:
-   gcc -Wall `pkg-config --cflags gl +   gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c

← Older revision		Revision as of 15:37, 29 March 2010
Line 246:		Line 246:

	You can compile this example with following command:		You can compile this example with following command:
-	gcc -Wall `pkg-config --cflags ~~glib-2.0, liblocation~~ --libs ~~glib-2.0,~~ liblocation` -o test test.c	+	gcc -Wall `pkg-config --cflags --libs liblocation` -o test test.c

	[[Category:Development]]		[[Category:Development]]
	[[Category:Documentation]]		[[Category:Documentation]]
	[[Category:Fremantle]]		[[Category:Fremantle]]

← Older revision		Revision as of 12:53, 12 February 2010
Line 247:		Line 247:
	You can compile this example with following command:		You can compile this example with following command:
	gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c		gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]

← Older revision		Revision as of 14:22, 3 December 2009
Line 69:		Line 69:


-	The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. ''LocationGPSDeviceFix'' fields are listed below. In ~~parenthesis~~ there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set.	+	The most useful field is naturally "fix" which contains position and movement of the device and accuracies for them. ''LocationGPSDeviceFix'' fields are listed in table below. In "Fields Flag" column there is a identifier which can be bitwisely anded with "fields" field, to see whether corresponding field is set.

		+	{\| class="wikitable" style="margin: 1em auto 1em auto"
		+	\|+LocationGPSDeviceFix
		+	! Variable !! colspan="3" \| Description
		+	\|-
		+	\| mode \|\| colspan="3" \| Mode of the fix (2D, 3D, not seen or no fix)
		+	\|-
		+	\| fields \|\| colspan="3" \| Bitfield representing what fields contain valid data
		+	\|-
		+	! Variable !! Unit !! Description !! Fields Flag
		+	\|-
		+	\| time \|\| s \|\| Timestamp of the update \|\| LOCATION_GPS_DEVICE_TIME_SET
		+	\|-
		+	\| ept \|\| s \|\| Time accuracy
		+	\|-
		+	\| latitude \|\| degrees \|\| Fix latitude \|\| LOCATION_GPS_DEVICE_LATLONG_SET
		+	\|-
		+	\| longitude \|\| degrees \|\| Fix longitude \|\| LOCATION_GPS_DEVICE_LATLONG_SET
		+	\|-
		+	\| eph \|\| cm \|\| Horizontal position accuracy
		+	\|-
		+	\| altitude \|\| m \|\| Fix altitude \|\| LOCATION_GPS_DEVICE_ALTITUDE_SET
		+	\|-
		+	\| epv \|\| m \|\| Altitude accuracy
		+	\|-
		+	\| track \|\| degrees \|\| Direction of motion \|\| LOCATION_GPS_DEVICE_TRACK_SET
		+	\|-
		+	\| epd \|\| degrees \|\| Track accuracy
		+	\|-
		+	\| speed \|\| km/h \|\| Current speed \|\| LOCATION_GPS_DEVICE_SPEED_SET
		+	\|-
		+	\| eps \|\| km/h \|\| Speed accuracy
		+	\|-
		+	\| climb \|\| m/s \|\| Current rate of climb \|\| LOCATION_GPS_DEVICE_CLIMB_SET
		+	\|-
		+	\| epc \|\| m/s \|\| Climb accuracy
		+	\|}

-	*LocationGPSDeviceMode mode: The ~~mode of the fix~~	+	The units for epv, epd, eps and epc might be different in liblocation version 0.99-1 and older.
-	*guint32 fields: A bitfield representing what fields contain valid data	+
-	*double time: The timestamp of the update (LOCATION_GPS_DEVICE_TIME_SET)	+
-	*double ept: Time accuracy	+
-	*double latitude: Fix latitude (LOCATION_GPS_DEVICE_LATLONG_SET)	+
-	*double longitude: Fix longitude (LOCATION_GPS_DEVICE_LATLONG_SET)	+
-	*double eph: Horizontal position accuracy	+
-	*double altitude: Fix altitude in meters (LOCATION_GPS_DEVICE_ALTITUDE_SET)	+
-	*double epv~~: Vertical position accuracy~~	+
-	*double track: Direction of motion in degrees (LOCATION_GPS_DEVICE_TRACK_SET)	+
-	*double epd~~: Track accuracy~~	+
-	*double speed: Current speed in km/h (LOCATION_GPS_DEVICE_SPEED_SET)	+
-	*double eps~~: Speed accuracy~~	+
-	*double climb: Current rate of climb in ~~m/s (LOCATION_GPS_DEVICE_CLIMB_SET)~~	+
-	*double epc: Climb accuracy	+
-		+

	An application receiving a fix cannot know if the fix is a result from location method it requested. Therefore application should study whether fix is accurate enough to satisfy application's needs. This can be done by inspecting "eph" field, which is fix's horizontal accuracy in centimeters. Typical values for horizontal accuracies can be seen in the location methods table. If accuracy is not known, it has a value of NaN.		An application receiving a fix cannot know if the fix is a result from location method it requested. Therefore application should study whether fix is accurate enough to satisfy application's needs. This can be done by inspecting "eph" field, which is fix's horizontal accuracy in centimeters. Typical values for horizontal accuracies can be seen in the location methods table. If accuracy is not known, it has a value of NaN.
-

	==Liblocation signals and callbacks==		==Liblocation signals and callbacks==

← Older revision		Revision as of 13:22, 3 December 2009
Line 31:		Line 31:
	g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS \| LOCATION_METHOD_AGNSS, NULL);		g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS \| LOCATION_METHOD_AGNSS, NULL);

-	ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is any, an error to application is signalled.	+	ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is not any, an error to application is signalled.

	USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.		USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.

← Older revision		Revision as of 12:03, 25 September 2009
Line 46:		Line 46:
	\| ACWP \|\| 1km-10km \|\| Yes \|\| Yes \|\| No		\| ACWP \|\| 1km-10km \|\| Yes \|\| Yes \|\| No
	\|-		\|-
-	\| GNSS \|\| 1m-100m \|\| No \|\| No \|\| Yes	+	\| GNSS \|\| 5m-100m \|\| No \|\| No \|\| Yes
	\|-		\|-
-	\| AGNSS \|\| 1m-100m \|\| Yes \|\| Yes \|\| Yes	+	\| AGNSS \|\| 5m-100m \|\| Yes \|\| Yes \|\| Yes
	\|}		\|}

← Older revision		Revision as of 12:01, 25 September 2009
Line 31:		Line 31:
	g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS \| LOCATION_METHOD_AGNSS, NULL);		g_object_set(G_OBJECT(control), "preferred-method", LOCATION_METHOD_GNSS \| LOCATION_METHOD_AGNSS, NULL);

-	ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there ~~isn't~~ any, an error to application is signalled.	+	ACWP and AGNSS methods require network positioning and GNSS and AGNSS require GPS to be enabled in location settings. If requirements for asked methods are not enabled when starting location, user is prompted a dialog to enable them. After that all the possible preferred-methods are started. If there is any, an error to application is signalled.

	USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.		USER_SELECTED method makes expection to dialog rule. Albeit it uses all of the methods: CWP+ACWP+GNSS+AGNSS, dialog is shown only if both networking and gps are disabled.

← Older revision		Revision as of 14:33, 24 September 2009
Line 162:		Line 162:
	#include <location/location-gpsd-control.h>		#include <location/location-gpsd-control.h>

-	static void on_error(LocationGPSDControl *control, gpointer data)	+	static void on_error(LocationGPSDControl *control, LocationGPSDControlError error, gpointer data)
	{		{
-	g_debug("location error... quitting");	+	g_debug("location error: %d... quitting", error);
	g_main_loop_quit((GMainLoop *) data);		g_main_loop_quit((GMainLoop *) data);
	}		}
Line 211:		Line 211:
	NULL);		NULL);

-	g_signal_connect(control, "error", G_CALLBACK(on_error), loop);	+	g_signal_connect(control, "error-verbose", G_CALLBACK(on_error), loop);
	g_signal_connect(device, "changed", G_CALLBACK(on_changed), control);		g_signal_connect(device, "changed", G_CALLBACK(on_changed), control);
	g_signal_connect(control, "gpsd-stopped", G_CALLBACK(on_stop), loop);		g_signal_connect(control, "gpsd-stopped", G_CALLBACK(on_stop), loop);
Line 226:		Line 226:

	You can compile this example with following command:		You can compile this example with following command:
-	gcc -Wall `pkg-config --cflags gl	+	gcc -Wall `pkg-config --cflags glib-2.0, liblocation --libs glib-2.0, liblocation` -o test test.c