Re: Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]

2010-01-03 Thread Cornelius Hald
On Fri, 2010-01-01 at 13:24 +0100, ds wrote: Cornelius Hald gave the following tip: They key constants for the +/- keys are the same as on Diablo. But before you can use them you first have to unmap the default action, which is sound volume up/down. How do I unmap the default action??

Re: Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]

2010-01-03 Thread Faheem Pervez
It was also thought about in Hildon (http://maemo.gitorious.org/hildon/hildon/blobs/master/hildon/hildon-gtk.c#line455) so it's probably time for me to remove that function soon... Best Regards, Faheem On Sun, Jan 3, 2010 at 10:45 AM, Cornelius Hald h...@icandy.de wrote: On Fri, 2010-01-01 at

Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]

2010-01-01 Thread ds
Cornelius Hald gave the following tip: They key constants for the +/- keys are the same as on Diablo. But before you can use them you first have to unmap the default action, which is sound volume up/down. How do I unmap the default action?? I could not find it in the documentation:-(

Re: Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]

2010-01-01 Thread Martin Grimme
Hi, you have to set an XAtom on your window. This is how I do it in Python: self.__window.window.property_change(_HILDON_ZOOM_KEY_ATOM, XA_INTEGER, 32, gtk.gdk.PROP_MODE_REPLACE,