Using Fremantle widgets - Revision history

amigadave: /* Testing Hardware Orientation In Scratchbox */ copy information from ForceRotation

amigadave — Wed, 04 May 2011 08:51:24 GMT

Testing Hardware Orientation In Scratchbox: copy information from ForceRotation

← Older revision		Revision as of 08:51, 4 May 2011
Line 433:		Line 433:

	Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.		Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.
		+
		+	=== Forcing screen rotation ===
		+
		+	If you need a way to force some rotation of your N900 screen, this is for you.
		+
		+	<source lang="c">
		+	/*
		+	gcc rotate.c -lX11 -lXrandr
		+	*/
		+	#include <X11/Xlib.h>
		+	#include <X11/extensions/Xrandr.h>
		+
		+	static void set_rotation (Rotation r_to) {
		+	Rotation r;
		+	int screen = -1;
		+	XRRScreenConfiguration* config;
		+	int current_size=0;
		+
		+	Display* display;
		+	Window rootWindow;
		+
		+	display = XOpenDisplay(":0");
		+	if (display == NULL) {
		+	return;
		+	}
		+
		+	screen = DefaultScreen(display);
		+	rootWindow = RootWindow(display, screen);
		+	XRRRotations(display, screen, &r);
		+	config = XRRGetScreenInfo(display, rootWindow);
		+	current_size = XRRConfigCurrentConfiguration (config, &r);
		+	XRRSetScreenConfig(display, config, rootWindow, current_size, r_to, CurrentTime);
		+	}
		+
		+	int main (int argc, char *argv[]) {
		+	set_rotation(RR_Rotate_90);
		+	//set_rotation(RR_Rotate_270);
		+	//set_rotation(RR_Rotate_180);
		+	//set_rotation(RR_Rotate_0);
		+	}
		+	</source>

	=== Testing Hardware Orientation In Scratchbox ===		=== Testing Hardware Orientation In Scratchbox ===

amigadave: wikify section headings, use `and`


amigadave — Wed, 04 May 2011 08:42:11 GMT
wikify section headings, use <code> and <source>
Show changes



amigadave: wikify
amigadave — Fri, 19 Feb 2010 08:34:32 GMT
wikify

		
		
		
		
		
		
		← Older revision
		Revision as of 08:34, 19 February 2010
		
		Line 1:
Line 1:
- This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment. + This document should help developers to port the user interface from [[Open development/Maemo roadmap/Diablo|Diablo]] to [[Open development/Maemo roadmap/Fremantle|Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
- in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation: + in addition, please check the growing [[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines|Human Interface Guidelines]] and the official hildon documentation:
 * [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]  * [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
 * [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]  * [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]




dneary: Using Fremantle Widgets moved to Using Fremantle widgets: Capitalisation
dneary — Fri, 13 Nov 2009 17:24:00 GMT
Using Fremantle Widgets moved to Using Fremantle widgets: Capitalisation

		
		
		
		
		
		
		← Older revision
		Revision as of 17:24, 13 November 2009
		
		



192.100.124.219: /* Portrait Mode */
192.100.124.219 — Thu, 12 Nov 2009 09:28:36 GMT
Portrait Mode

		
		
		
		
		
		
		← Older revision
		Revision as of 09:28, 12 November 2009
		
		Line 217:
Line 217:
 * The toolbar is not wide enough to hold all items anymore.  * The toolbar is not wide enough to hold all items anymore.
 * The columns of your tree view get too small.  * The columns of your tree view get too small.
- * You cannot enter text because there´s no onscreen keyboard. + * You cannot enter text because there´s no onscreen keyboard.  (Actually the FKB works perfectly, but it will switch to landscape and then back to portrait when closed.)
-   (Actually the FKB works perfectly, but it will switch to landscape + 
-    and then back to portrait when closed.) + 
 * Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).  * Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
 * Probably more...  * Probably more...




192.100.124.218: /* Portrait Mode */
192.100.124.218 — Thu, 12 Nov 2009 09:27:31 GMT
Portrait Mode

		
		
		
		
		
		
		← Older revision
		Revision as of 09:27, 12 November 2009
		
		Line 218:
Line 218:
 * The columns of your tree view get too small.  * The columns of your tree view get too small.
 * You cannot enter text because there´s no onscreen keyboard.  * You cannot enter text because there´s no onscreen keyboard.
  +   (Actually the FKB works perfectly, but it will switch to landscape
  +    and then back to portrait when closed.)
 * Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).  * Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
 * Probably more...  * Probably more...
Line 271:
Line 273:
  
 Whether or not your application is rotated depends on a couple of things:  Whether or not your application is rotated depends on a couple of things:
- * There are two flags which you can set on your windows. Those flags tell the system what to do.   + * There are two X window properties which you can set on your windows.
  + * Those tell the system what to do.  The type of the value of the properties is <tt>XA_CARDINAL</tt> where 0 means "off", and 1 stands for "on".  Other values may get other meaning in the future.
 ** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.  ** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.
 ** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.  ** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.
 * Rotation only happens when all visible windows are ok with being rotated.  * Rotation only happens when all visible windows are ok with being rotated.
  
- That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set and at least one application must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set. + That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set to 1 and at least one of them must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set to true.  The flags are inherited through the transiency chain, so you needn't set the SUPPORT flag on your transient dialogs for example, nor on all stackable windows.
  
 It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.  It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.
Line 284:
Line 287:
 * During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.  * During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
 * While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.    * While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.  
- Currently it's necessary to set 'request' always together with 'support' as 'request' does not imply 'support'. + It is not necessary to set 'request' together with 'support' as 'request' implies 'support', provided that 'support' is unset (as opposed to set to 0).
  
 === Finding Out The Current Hardware Orientation ===  === Finding Out The Current Hardware Orientation ===




guaka at 09:27, 26 October 2009
guaka — Mon, 26 Oct 2009 09:27:44 GMT


		
		
		
		
		
		
		← Older revision
		Revision as of 09:27, 26 October 2009
		
		Line 1:
Line 1:
- This document should help developers to port the user interface from Diablo to Fremantle. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment. + This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
 in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:  in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:
 * [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]  * [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]




pycage: fixed wrong piece of information about rotation WM flags
pycage — Thu, 08 Oct 2009 08:54:41 GMT
fixed wrong piece of information about rotation WM flags

		
		
		
		
		
		
		← Older revision
		Revision as of 08:54, 8 October 2009
		
		Line 283:
Line 283:
 * On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.  * On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.
 * During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.  * During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
- * While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag. There is no need to set both flags as 'request' also implies 'support'. + * While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.  
-   + Currently it's necessary to set 'request' always together with 'support' as 'request' does not imply 'support'.
  
 === Finding Out The Current Hardware Orientation ===  === Finding Out The Current Hardware Orientation ===




thp: /* Listening To Hardware Orientation Changes (Python example) */
thp — Mon, 21 Sep 2009 22:57:10 GMT
Listening To Hardware Orientation Changes (Python example)

		
		
		
		
		
		
		← Older revision
		Revision as of 22:57, 21 September 2009
		
		Line 412:
Line 412:
 # Start the main loop - only needed for console apps  # Start the main loop - only needed for console apps
 mainloop.run()</pre>  mainloop.run()</pre>
  + 
  + Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.
  
 == Testing Hardware Orientation In Scratchbox ==  == Testing Hardware Orientation In Scratchbox ==




thp: /* Automatic Screen Rotation */
thp — Mon, 21 Sep 2009 22:14:42 GMT
Automatic Screen Rotation

		
		
		
		
		
		
		← Older revision
		Revision as of 22:14, 21 September 2009
		
		Line 382:
Line 382:
 dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);  dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);
 </pre>  </pre>
  + 
  + === Listening To Hardware Orientation Changes (Python example) ===
  + 
  + This short snippet should get you started (you only need the gobject.MainLoop if you are writing a console application). "handler" will be called every time the orientation changes, and the first parameter is the important one (compare it to "landscape" and "portrait").
  + 
  + <pre>import dbus
  + import dbus.glib
  + 
  + # Again, this is only needed for console apps
  + import gobject
  + mainloop = gobject.MainLoop()
  + 
  + # Define some constants
  + MCE_SIGNAL_NAME = 'sig_device_orientation_ind'
  + MCE_SIGNAL_IFACE = 'com.nokia.mce.signal'
  + MCE_SIGNAL_PATH = '/com/nokia/mce/signal'
  + 
  + # Get the system bus
  + system_bus = dbus.Bus.get_system()
  + 
  + # Define a callback that gets called for orientation changes
  + def handler(orientation, stand, face, x, y, z):
  +     print orientation
  + 
  + # Connect the "handler" to the orientation changed signal of mce
  + system_bus.add_signal_receiver(handler, signal_name=MCE_SIGNAL_NAME, \
  +         dbus_interface=MCE_SIGNAL_IFACE, path=MCE_SIGNAL_PATH)
  + 
  + # Start the main loop - only needed for console apps
  + mainloop.run()</pre>
  
 == Testing Hardware Orientation In Scratchbox ==  == Testing Hardware Orientation In Scratchbox ==

← Older revision		Revision as of 08:34, 19 February 2010
Line 1:		Line 1:
-	This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.	+	This document should help developers to port the user interface from [[Open development/Maemo roadmap/Diablo\|Diablo]] to [[Open development/Maemo roadmap/Fremantle\|Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
-	in addition, please check the growing [~~http://wiki.maemo.org/index.php?title=~~Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:	+	in addition, please check the growing [[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines\|Human Interface Guidelines]] and the official hildon documentation:
	* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]		* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
	* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]		* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]

← Older revision		Revision as of 09:28, 12 November 2009
Line 217:		Line 217:
	* The toolbar is not wide enough to hold all items anymore.		* The toolbar is not wide enough to hold all items anymore.
	* The columns of your tree view get too small.		* The columns of your tree view get too small.
-	* You cannot enter text because there´s no onscreen keyboard.	+	* You cannot enter text because there´s no onscreen keyboard. (Actually the FKB works perfectly, but it will switch to landscape and then back to portrait when closed.)
-	(Actually the FKB works perfectly, but it will switch to landscape	+
-	and then back to portrait when closed.)	+
	* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).		* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
	* Probably more...		* Probably more...

← Older revision		Revision as of 09:27, 12 November 2009
Line 218:		Line 218:
	* The columns of your tree view get too small.		* The columns of your tree view get too small.
	* You cannot enter text because there´s no onscreen keyboard.		* You cannot enter text because there´s no onscreen keyboard.
		+	(Actually the FKB works perfectly, but it will switch to landscape
		+	and then back to portrait when closed.)
	* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).		* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
	* Probably more...		* Probably more...
Line 271:		Line 273:

	Whether or not your application is rotated depends on a couple of things:		Whether or not your application is rotated depends on a couple of things:
-	* There are two ~~flags~~ which you can set on your windows. Those ~~flags~~ tell the system what to do.	+	* There are two X window properties which you can set on your windows.
		+	* Those tell the system what to do. The type of the value of the properties is <tt>XA_CARDINAL</tt> where 0 means "off", and 1 stands for "on". Other values may get other meaning in the future.
	** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.		** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.
	** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.		** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.
	* Rotation only happens when all visible windows are ok with being rotated.		* Rotation only happens when all visible windows are ok with being rotated.

-	That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set and at least one ~~application~~ must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set.	+	That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set to 1 and at least one of them must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set to true. The flags are inherited through the transiency chain, so you needn't set the SUPPORT flag on your transient dialogs for example, nor on all stackable windows.

	It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.		It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.
Line 284:		Line 287:
	* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.		* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
	* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.		* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.
-	~~Currently it's~~ necessary to set 'request' ~~always~~ together with 'support' as 'request' ~~does not imply~~ 'support'.	+	It is not necessary to set 'request' together with 'support' as 'request' implies 'support', provided that 'support' is unset (as opposed to set to 0).

	=== Finding Out The Current Hardware Orientation ===		=== Finding Out The Current Hardware Orientation ===

← Older revision		Revision as of 09:27, 26 October 2009
Line 1:		Line 1:
-	This document should help developers to port the user interface from Diablo to Fremantle. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.	+	This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
	in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:		in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:
	* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]		* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]

← Older revision		Revision as of 08:54, 8 October 2009
Line 283:		Line 283:
	* On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.		* On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.
	* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.		* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
-	* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag. ~~There is no need~~ to set ~~both flags~~ as 'request' ~~also implies~~ 'support'.	+	* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.
-		+	Currently it's necessary to set 'request' always together with 'support' as 'request' does not imply 'support'.

	=== Finding Out The Current Hardware Orientation ===		=== Finding Out The Current Hardware Orientation ===

← Older revision		Revision as of 22:57, 21 September 2009
Line 412:		Line 412:
	# Start the main loop - only needed for console apps		# Start the main loop - only needed for console apps
	mainloop.run()</pre>		mainloop.run()</pre>
		+
		+	Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.

	== Testing Hardware Orientation In Scratchbox ==		== Testing Hardware Orientation In Scratchbox ==

← Older revision		Revision as of 22:14, 21 September 2009
Line 382:		Line 382:
	dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);		dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);
	</pre>		</pre>
		+
		+	=== Listening To Hardware Orientation Changes (Python example) ===
		+
		+	This short snippet should get you started (you only need the gobject.MainLoop if you are writing a console application). "handler" will be called every time the orientation changes, and the first parameter is the important one (compare it to "landscape" and "portrait").
		+
		+	<pre>import dbus
		+	import dbus.glib
		+
		+	# Again, this is only needed for console apps
		+	import gobject
		+	mainloop = gobject.MainLoop()
		+
		+	# Define some constants
		+	MCE_SIGNAL_NAME = 'sig_device_orientation_ind'
		+	MCE_SIGNAL_IFACE = 'com.nokia.mce.signal'
		+	MCE_SIGNAL_PATH = '/com/nokia/mce/signal'
		+
		+	# Get the system bus
		+	system_bus = dbus.Bus.get_system()
		+
		+	# Define a callback that gets called for orientation changes
		+	def handler(orientation, stand, face, x, y, z):
		+	print orientation
		+
		+	# Connect the "handler" to the orientation changed signal of mce
		+	system_bus.add_signal_receiver(handler, signal_name=MCE_SIGNAL_NAME, \
		+	dbus_interface=MCE_SIGNAL_IFACE, path=MCE_SIGNAL_PATH)
		+
		+	# Start the main loop - only needed for console apps
		+	mainloop.run()</pre>

	== Testing Hardware Orientation In Scratchbox ==		== Testing Hardware Orientation In Scratchbox ==

Using Fremantle widgets - Revision history

amigadave: /* Testing Hardware Orientation In Scratchbox */ copy information from ForceRotation

amigadave: wikify section headings, use and

amigadave: wikify

dneary: Using Fremantle Widgets moved to Using Fremantle widgets: Capitalisation

192.100.124.219: /* Portrait Mode */

192.100.124.218: /* Portrait Mode */

guaka at 09:27, 26 October 2009

pycage: fixed wrong piece of information about rotation WM flags

thp: /* Listening To Hardware Orientation Changes (Python example) */

thp: /* Automatic Screen Rotation */

amigadave: wikify section headings, use `and`