Notes: Hello! I can´t figure out how to add touch events at all. I was able to apply mouse events, since these are listed in the event type list of elements, like mousemove, mouseenter, mouseleave and so on, but there is no adequate type for touch events.
There are two event types: swipeleft, swipright, but both don´t do anything, as far as i can see.
Mouse down, mouse up and mouse click events should works well on touch devices as touch start, touch end, tap events respectively.
Mouse move related events (move, enter/leave, over/out) should not be used on touch devices (though they works on Android, and latest iOS).
Swipe left/right should work as expected. Can you please let me know which browser and OS you’re testing on?
I am on Google Chrome on a Microsoft Surface Device with Touchscreen. Mouseevents work nicely, but no touchevents here, also no “swipe left/right”.
However Chrome Developer tools provide a setting to simulate touch events when using a mouse. Using this touch device simulation at least the “swipe left/right” works, but still no mousemoves at all.
I am trying to trigger javascript functions, at the moment they simply write something out via console.log. All functions are hooked and working, since the mousemove is triggered when using a mouse, and the swipe-function too, when simulating touch events.
Just to let you know: I am programming javascript touch/mouse events a lot outside Saola, so I think I know what I am doing.
Swipe left/right works well on my Android phone.
I don’t have a Surface to check now, but I guess it might be a bug on Windows with touch screens.
I’ll check and let you know later.
About other touch events, can you please provide an use case? Which types of events do you need and what do you intend to do with them?
I can’t imagine it to be an issue of Windows touch devices, since everything programmed with Adobe Dreamweaver or Chrome runs fine. Actually my business is interactive images, and I am using the Surface when presenting them at meetings.
E.g. this page runs fine on my surface, using either the mouse or the touch screen:
We’ve tested again and found that it’s indeed a bug of swipe event on Windows touch devices only.
We’ll fix it in the next update.
Can you please help us to check if the attached HTML5 works on your Surface? swipe_HTML5.zip (42.9 KB)
Regarding mousemove event, I forgot that it doesn’t support continuous mouse movement on touch devices. We’ll consider supporting it in the future.
If you know JavaScript, you can add Run JavaScript action to Scene Activate event to handle touch/mouse move as in the attached project. touch move.saolapack (2.1 KB)
Thanks Mack for your kind help.
I just want to confirm that you did swipe on the white area? Swipe may not work on the blue area that shows the logs. Moreover, in this test sample I set a quite small angle tolerance, so please swipe in nearly horizontal direction.
Thanks again for your help.
I now also tested the Saolapack you sent. And indeed, with the workaround I got touch events now. That’s exactly what I needed so far, at least I have them on all devices. However it would be great to be able to attach them on element level from within the gui. So I hope you can fix it for the next update, I purchsed Saola yesterday.
The Swipe left/right-test you sent works when keeping the movement very horizontically.
Hello, I didn’t use Saola Animate for more almost two years now, but nowadays I did again.
I once again struggled with the touch events and remebered this thread here. I did not change anything, still Saola Animate does not support touch events natively, right? So I still have to hassle around with this workaround?
I am really astonished that no updates for the software were made for almost two years now. Is that true?
We’ll release version 3.0 soon with notable features such as exporting to video, preset effects and text animations, morphing animation…
Unfortunately, there is still no touchmove event yet. Instead, we have plan to support drag event (which works with both mouse and touch events) after version 3.0.
Oh, I was so happy to get the version 3.0, hoping there would be support for touch screens now, either with drag or touch vents. Then I recognized it will be supported “after” version 3.0.
It’s simple for almost all use cases, but it’s hard for some use cases.
A feature must work well on all use cases, not like a workaround, so it’s hard to implement.