@13Flo
Short answer — no, not now, it won't work with Touch and Mouse events (StarlingInputAdapter) at the same time.
Long answer — pfff too long to answer. But basically it's why it's "alpha" and why I put it to public... expecting some interest and help from the community, but with no luck.
Finally I got some time to release v0.4
https://github.com/downloads/fljot/Gestouch/gestouch-0.4.swc
Initialization API has changed a bit since beta version, but still nothing tricky. You can see example in the README.
One important change though — rotation (for RotateGesture and TransformGesture) is now in radians rather then degrees. No other changes that might bother you.
Those who started using it already — please try that out and report if anything doesn't seem right.
@pavel.fljot how I use swipe event ?
@fukhaos
have you checked examples?
I checked in this example:
https://github.com/fljot/GestouchExamples/tree/master/src/org/gestouch/examples/starling,
but don't find the swipe event.
As I wrote, there's absolutely no difference how it works with Starling or native display objects:
var swipe:SwipeGesture = new SwipeGesture(target);
// optional: swipe.direction = SwipeGestureDirection. ...
swipe.addEventListener(GestureEvent.GESTURE_RECOGNIZED, onSwipe);
function onSwipe(event:GestureEvent):void
{
}
why ?
mStarling = new Starling(Game, stage, viewPort, null, Context3DRenderMode.AUTO, "baseline"); mStarling.stage3D.addEventListener(Event.CONTEXT3D_CREATE, function(e:Event):void { // Starling is ready! We remove the startup image and start the game. removeChild(startupImage); mStarling.start(); Gestouch.inputAdapter ||= new NativeInputAdapter(stage); Gestouch.addDisplayListAdapter(starling.display.DisplayObject, new StarlingDisplayListAdapter()); Gestouch.addTouchHitTester(new StarlingTouchHitTester(mStarling), -1); });
error: TypeError: Error #1034: Type Coercion failed: cannot convert to org.gestouch.core.IInputAdapter.
at Function/Main.as$0:anonymous()[/Users/.../src/Main.as:79]
@kemury
honestly don't know. As far as I remember error message shouldn't look like that. It should specify "cannot convert ### to ###".
I tested my starling examples with the last swc (0.4.3) — works fine. Maybe you have some mess with source files and swc?
I couldn't find the gestouch.swc (0.4.3) in GitHub ?
Have you checked downloads section?) https://github.com/fljot/Gestouch/downloads
Sorry about that 
but still don't work
same error
I am using the Starling Mobile Scalfold
and Air 3.4 in FB 4.7
They use new compiler in FB 4.7 right? Maybe that the issue... try to change "||=" to simply "=" (to make it clear why I wrote "||=" — it's because adapter can be already automatically initialized if you use Gestouch with native/classic DisplayObjects).
If doesn't work try with previous version of FB or with FlexSDK 4.6 (last one from Adobe) and command-line tools.
If still doesn't work (unlikely) send me the project to pavel.fljot at gmail.
I remove the "||="
and works !!!
but now the error is the:
var tap:TapGesture = new TapGesture(starlingSprite);
Error: Cannot create adapter for target [object Sprite] of type starling.display::Sprite. at org.gestouch.core::Gestouch$/org.gestouch.core::gestouch_internal::createGestureTargetAdapter()[/Users/fljot/projects/flash/velvet/Gestouch/src/org/gestouch/core/Gestouch.as:100] at org.gestouch.gestures::Gesture/set target()[/Users/fljot/projects/flash/velvet/Gestouch/src/org/gestouch/gestures/Gesture.as:129] at org.gestouch.gestures::Gesture()[/Users/fljot/projects/flash/velvet/Gestouch/src/org/gestouch/gestures/Gesture.as:87] at org.gestouch.gestures::AbstractDiscreteGesture()[/Users/fljot/projects/flash/velvet/Gestouch/src/org/gestouch/gestures/AbstractDiscreteGesture.as:20] at org.gestouch.gestures::TapGesture()[/Users/fljot/projects/flash/velvet/Gestouch/src/org/gestouch/gestures/TapGesture.as:29]
Seems like it's a bug with ||= operator
@kemury
seems like there are a lot of bugs in the new compiler.. I also use same kind of lazy assignment ( ||= ) in the library. And this error (if you properly added adapter before) is also the result of new compiler weirdness.
So for now either stick to the old compiler, or try to investigate new compiler issues yourself (I don't want to touch it till new compiler is about to be released).
ASC 2.0 Preview 2 is out. Someone may try out if it works fine now)
FB 4.7p uses that already. This is just made standealone for everyone else.
@M3wThr33 Are you sure? FB4.7 uses ASC 2.0, but I don't think it included Preview 2.
If you read the installation instructions it mentions that 4.7 already includes it and there's no installation needed. (But this IS Adobe... I guess it wouldn't hurt to try)
As for the compile issues:
Digging into this issue, I've been trying to get it past the crashes.
One thing I did was to change initClass in Gestouch.as to add a starling.display.DisplayObject in addition to a flash.display.DisplayObject, but I noticed the new NativeDisplayListAdapter doesn't pass in any values.
And without values, the displayListAdapters array never get initialized with any data outside of null.
So, when I try to instantiate a SwipeGesture pointing to a Starling Sprite, it can find a compatible adapter entry in the displayListAdapters, but it's a null entry.
No matter how successful this line is:
Gestouch.gestouch_internal::getDisplayListAdapter(target); (line 97 in Gestouch.as)
It'll always return null as long as NativeDisplayListAdapter is instantianted with null.
As I understand it, FB 4.7 included the first build of ASC 2.0. Adobe doesn't always update every detail of the release notes. The first preview build was released at the same time as FB 4.7. When the second preview build was released, I don't think there was a FB 4.7 update released at the same time. Ultimately, my point is that yes, FB 4.7 has ASC 2.0, but it may be a older build than the more recent preview 2. Looking through the release notes, it doesn't say anything about the specific build that FB 4.7 includes.
That said, I remember seeing an "check for AIR SDK updates" type of link in FB 4.7. That may be why there wasn't a new build of FB 4.7. I'd be curious to know if that link is able to update to preview 2 or not.
@kemury
I was able to get gestouch working with FB 4.7 but had similar problems with the ||=. I think your current error is a order of execution problem. Your game instance is being created before you've properly initialized gestouch. Try this change, add the gstouch adaptors immediately after you create the starling instance. Then add the gesture events as you have been before. This worked fine for me.
mStarling = new Starling(Game, stage, viewPort); Gestouch.inputAdapter = new NativeInputAdapter(stage); Gestouch.addDisplayListAdapter(starling.display.DisplayObject, new StarlingDisplayListAdapter()); starlingTouchHitTester = new StarlingTouchHitTester(mStarling); Gestouch.addTouchHitTester(starlingTouchHitTester, -1); mStarling.stage3D.addEventListener(Event.CONTEXT3D_CREATE, function(e:Event):void { // Starling is ready! We remove the startup image and start the game. removeChild(startupImage); mStarling.start(); mStarling.showStats = true; });
@Matt Summers
To be honest I don't see how this kind of order of execution could affect anything. I mean normally (with the old good mxmlc) it doesn't matter when you initialize StarlingTouchHitTester and register (add) it. Well the only thing is that it requires Starling instance, so it has to go after Starling instance creation. But no actual processing happens until interaction starts.
Anyway, again, I don't officially touch anything for now until new compiler is released. I hope Adobe will finally do a decent job.
@pavel.fljot
Moving the code to just after the starling instance was created fixed the error that I was getting in Flash Builder 4.7:
"Cannot create adapter for target [object Sprite] of type starling.display::Sprite."
Which is the same error that kemury is/was getting. In his code example above he was initializing Gestouch.addDisplayListAdapter after the CONTEXT3D_CREATE event listener has fired for his starling instance. While debugging that issue in FB 4.7 we (myself and another developer) noticed that Game class was being created before the Starling Display List adapter was initialized, resulting in the gesture event being created before gestouch was setup. So after changing the ||= to just = (fixing the first error) and moving the adapter code to just after the starling instance was created I was able to add gesture events in the app without any further problems (so far at least!)
The ||= issue is definitely a quirk/bug of the new compiler in FB 4.7, but this is what I did to work around the 2 errors mentioned in this post.
@Matt Summers
Oh! You mean there are some gestures (defined and initialized) in Game that was happening before proper DisplayListAdapter was added (and therefore no adapter was found for those starling targets)? Yep, in this case it is better to move line
Gestouch.addDisplayListAdapter(starling.display.DisplayObject, new StarlingDisplayListAdapter());
above everything to make it bulletproof. Other configuration should be fine. So it this case I don't see any compiler bugs, it should work same way with both.
@kemury
be sure to read that stuff above! It should solve your issue with the new compiler.
@pavel.fljot
BTW, Thank you for the great library!
@Matt Summers
any released projects? Would be useful for the library and me as I will look for a job soon.
@pavel.fljot
Hi, and thank you for the lib, it is great.
I have a question I couldn't find an answer about : is it possible for a child displayobject to override a gesture of its parent? I'm trying to react to a long press, but only if it is not on a distinct child (a button). right now both gestures are recognized.
in my overall parent (which is Episode.current) I use this
m_press = new LongPressGesture(this); m_press.minPressDuration = 100 m_press.addEventListener(GestureEvent.GESTURE_BEGAN, press_handler); m_press.addEventListener(GestureEvent.GESTURE_ENDED, release_handler);
var press:Gesture = new LongPressGesture(m_button);//a member button of the child press.addEventListener(GestureEvent.GESTURE_POSSIBLE, onButtonGesture); press.addEventListener(GestureEvent.GESTURE_BEGAN, onButtonGesture); [...] private function onButtonGesture(_event:GestureEvent):void{ _event.stopImmediatePropagation(); _event.preventDefault(); //(_event.target as Gesture).requireGestureToFail(Episode.current.pressGesture); //(_event.target as Gesture).requireGestureToFail(Episode.current.tapGesture); }
I commented the "requireGestureToFail()" calls since they didn't seem to work.
Did I miss something?
Thanks.
@resistcorp
I didn't get what are you trying to achieve, but GestureEvent is not propagating (since it's not DisplayList event) and it has not default actions, so calling those methods on event is pretty much useless. I don't know where did you see that kind of usage or why would you think it should work.
Same for "requireGestureToFail()" — examples project clearly shows how to use that.
You must log in to post.
