Re: [Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798

2012-08-14 Thread Simon Schampijer
On 08/09/2012 10:27 PM, Manuel QuiƱones wrote: Thanks Gonzalo, Thanks Gonzalo. I was intrigued by that fact and looked a bit at the issue. 2012/8/9 godi...@sugarlabs.org: From: Gonzalo Odiard godi...@gmail.com Use clicked instead of button-pressed, because this is not triggered by touch

Re: [Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798

2012-08-14 Thread Gonzalo Odiard
I am fine to go with 'clicked' as Gonzalo suggested but would be nice to know the details as well. Regards, Simon The following info can be related: In gtk3, a patch to check emulating_pointer before use touch as button_press/release:

[Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798

2012-08-09 Thread godiard
From: Gonzalo Odiard godi...@gmail.com Use clicked instead of button-pressed, because this is not triggered by touch device. Signed-off-by: Gonzalo Odiard gonz...@laptop.org --- src/sugar3/graphics/window.py | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

Re: [Sugar-devel] [sugar-toolkit-gtk3] Replace signal used in UnfullscreenButton to enable use with touch - SL #3798

2012-08-09 Thread Manuel QuiƱones
Thanks Gonzalo, 2012/8/9 godi...@sugarlabs.org: From: Gonzalo Odiard godi...@gmail.com Use clicked instead of button-pressed, because this is not triggered by touch device. Makes sense, clicked is more general than button-pressed. From the docs, is emitted when the button has been