Needs to bind unnecessary events.


can't just bind one of swipe events. Need to bind @swipeone@ event first!

NOT work



gurustump wrote Mar 14, 2013 at 7:31 AM

I've actually run into the same problem. It appears that swiperight and swipeleft simply don't work. I wasn't able to use the workaround that SerzN1 tried (putting a swipeone event listener in the code before the swipeleft and swiperight ones) so I ended up writing my own equation to determine the direction of the swipe inside the swipeone event handler.

In any case, I don't know that this bug should be considered of Low impact. My guess is that swipeleft and swiperight are among the most used event handlers in this plugin's repertoire. If I get some time, I'll try to see what's going wrong in there. Cheers.

wrote Mar 14, 2013 at 7:32 AM

wrote Mar 26, 2013 at 12:47 PM

Petrux99 wrote Mar 26, 2013 at 12:54 PM

Same thing here - swiperight and swipeleft never fire, only swiperightup and swiperightdown etc. For me binding swipeone didn't help either. I tried to hack the treshold for allowing more vertical movement (it seems to only accept zero pixels??), but for some reason I couldn't get it working.

I definitely agree that this can't be considered low impact.

wrote Jan 4, 2014 at 12:26 PM

NicolasBernier wrote Jan 4, 2014 at 12:40 PM

This is obviously a bug to me. I modified the script (0.90 version) to make swiperight and friends to work the way that seems the simplest to me : only the closest of the 8 directions is triggered. For example, swiping up will trigger swipeup, even if it's slightly on the left or on the right. If you expect swipeup but you swipe up left (or close to left up), swipe up won't trigger.

I also added the name attribute (left, rigntdown) in the direction data for convenience.

Check out http://pastebin.com/yY0G3B6R

NicolasBernier wrote Jan 4, 2014 at 12:41 PM