Re: [SailfishDevel] Swipe lock (contd.)

2014-01-02 Thread Mikko Harju
On 01.01.2014 19:13, Bob Jelica wrote: > Continuing on the thread here: > https://lists.sailfishos.org/pipermail/devel/2013-November/001517.html > > Swipe lock using flags as per the thread above doesn’t work, neither emu nor > the device. > > Any other suggestions I could try? > I have a map i

Re: [SailfishDevel] Closing an application without killing the main loop

2013-12-12 Thread Mikko Harju
On 11.12.2013 22:51, Ville Ranki wrote: > I have not found a way to do it in Sailfish. When user closes the > application, Sailfish terminates the Qt main loop which effectively > makes it impossible to do any asynchronous tasks. Have you ran it on the actual device? It might be that the fix did

Re: [SailfishDevel] Swipe Lock

2013-12-03 Thread Mikko Harju
On 02.12.2013 18:32, Mariano Boragno wrote: > Hi Mikko, > > It's good to know that!! however now I have two concerns, then: > > 1. I would like to enable/disable the swipe lock on the fly (I could > live without this including a "quit" item in the pulley-menu). You can enable / disable it o

Re: [SailfishDevel] Swipe Lock

2013-12-02 Thread Mikko Harju
On 29.11.2013 21:42, Mariano Boragno wrote: > Hi guys, > > Anyway, this didn't work. I've set the Qt::WindowOverridesSystemGestures > as Jonni proposed but I can still minimize and close the application > using the swipe gesture. > > This feature is a must in my application. The game is intended

Re: [SailfishDevel] DeclarativeGlassImageProvider

2013-11-20 Thread Mikko Harju
On 19.11.2013 23:54, David Reinhold wrote: > Hi, > > I’m having problems with this as well. Did you manage to solve this problem > Tero? The image shows up just fine without the provider but when using the > provider I get: > QFSFileEngine::open: No file name specified > QFSFileEngine::open: No

Re: [SailfishDevel] Double-tap detection

2013-11-11 Thread Mikko Harju
On 10.11.2013 12:15, Artem Marchenko wrote: > Thanks, for the reply, Jonni, now I know about double clicks. Will do > own detection then. Hello Artem :) It seems double clicks are missed if the Flickable pressDelay is non-zero (and SilicaFlickable has non-zero default pressDelay). -- mikkoh _