View Single Post
Posts: 59 | Thanked: 168 times | Joined on Jun 2012
#393
Originally Posted by RobertMe View Post
It seems a bit odd to me, as I've added the code to not propagate the click/move to other elements, which, as you say, does work for the pagestack (without it you even couldn't go left/right as it would navigate between the pages). So it's odd the same fix doesn't apply to the pully. But the fix should be easy, I may be able to make a second release containing this fix later today.
I've just looked into this. Could it be you're swiping really fast (already making the swipe before touching the screen)? Because that's the only way I can reproduce it. When this happens the MouseArea which is used to track the swipe movement even doesn't receive the press/click, so it seems like there's nothing I can do about it. So I can only advice the work around of first pressing the screen, and then doing the swipe. You don't have to hold it for an eternity, but if you first touch the gesture pad and then start the swipe it works as it expected (or at least for me).

Coming back to the crash logging. There is no way to handle/log the crashes. Crashes may be logged by Sailfish itself. But for them to be useful it would require the presence of the debug symbols, which can't be provided in the store. So when you do get a crash, try to reproduce it and post the steps either here or send me an email. The same goes for other issues, either post them in this thread or email them to me and I will look into it.
 

The Following 2 Users Say Thank You to RobertMe For This Useful Post: