Air 3.1, currently all work prefect.
I use GPU mode, iOS 5.0.1 and iOS 4.3.3
MouseEvent.CLICK work prefect it you add this string Multitouch.inputMode = MultitouchInputMode.TOUCH_POINT; to your init class. Because by default in iOS used gestures.
Yeah, I'm seeing the same problem with MouseEvent.MOUSE_UP. Rendermode is set to auto, and I'm using the AIR 3.2 RC compiler.
Looks like the iOS stuff is getting confused about Z-ordering. If I have a movie clip on top of another movie clip, sometimes tapping will send the mouse event to the clip underneath the one that should be getting the event. For example, I have a big "PAUSE" movieclip that covers the entire screen, and tapping on it (i.e. the MOUSE_UP event) will dismiss it. If I tap on it, it won't get mouse-events, sometimes requiring a half-dozen taps. Meanwhile the stuff underneath the pause movieclip will receive the events.
Note that I am only seeing this on iOS. Android and Desktop are working properly.
Please provide sample code so I can test. Because all that you said - don't work for me.
also dont hesitate to use MovieClip.mouseChildren = false for included MCs to eachothers and MovieClip.mouseEnabled=false if you don't want affect MouseEvents for MCs.
Also for MobileDevices better use TouchEvent.TOUCH_TAP rather MouseEvent.CLICK
Can you please send a small application which can help us reproduce the bug and also please specify what renderMode you are using?Or you can log the bug with the bug files at bugbase.adobe.com .
Did this ever get resolved? I have an app waiting to go to the app store right now but I can't release it until I get this figured out. I'm noticing that the MouseEvent firing isn't consistent. The ActionBar is the problem area for me. My application is using RobotLegs and FB 4.6 (MXML based app) but I don't think that has anything to do with my issue.
Here are my trace statements from testing which actions get fired and if the action I am trying to take was successful or not.
1 - Works
2 - Works
3 - Works
4 - nothing happening, no click or touchTap event
5 - nothing happening, no click or touchTap event
6 - nothing happening, no click or touchTap event
7 - Working, repeated actionbar clicks
Partial code block:
<s:Button id="btnList" skinClass="spark.skins.mobile.BeveledActionButtonSkin" includeIn="map" width="40" height="40"
<fxg:iconList width="17" height="17" />
Any help or suggestion will be greatly appreciated!!!
Also, the TouchEvent.TOUCH_TAP doesn't solve the issue we are having.
Hi Markus ,
I am unable to reproduce this issue(with the provided code here on ios 4.3.5 and 5.1) with 3.2 build but I'll suggest you to use the latest build 3.3 available at http://labs.adobe.com/downloads/air3-3.html . If you still face the issue then please let us know .
What are the steps to install the AIR 3.3 SDK on a Mac? The usual overlay method isn't available because AIR 3.3 is a DMG file instead of a regular jar.
Thanks again for your help!
I would like to test out MouseEvent.RELEASE_OUTSIDE but can't seem to find it. I'm wondering if my overlay worked or if RELEASE_OUTSIDE is not available in Flash Builder 4.6. It would seem strange that it's only available in Flash CS 5.5 or 6.
Any thoughts on this?
I have tried both the Flash Builder 4.6 release build and the ADT ipa-debug-interpreter using the following SDKs
FB 4.6.0 AIR SDK 3.1 - came with 4.6
3.3 Beta - I was expecting to see MouseEvent.RELEASE_OUTSIDE here but it was not available to me.
The command I used to overlay my original FB 4.6.0 AIR sdk is:
rsync -avz /Volumes/AIR\ SDK/ AIR3.3_4.6.0/
The device SDKs used to test with are:
iPod Touch 4 generation - iOS 5.1.1
iPad 2 HD - iOS 5.1.1
iPhone 4 - iOS 5.1.1
iPhone 4S - iOS 5.1.1
Sample Build script:
/Applications/Adobe\ Flash\ Builder\ 4.6/sdks/4.6.0/bin/adt -package -target ipa-debug-interpreter -provisioning-profile /Users/markusmcgee/Applications/SolsticeConsulting/BSPN_Mobile/BSPNMo bileApp/provisioning/XXXX.mobileprovision -storetype pkcs12 -keystore /Users/markusmcgee/Applications/SolsticeConsulting/BSPN_Mobile/BSPNMo bileApp/provisioning/Certificates.p12 -storepass XXXX BSPNMobileApp.ipa BSPNMobileApp-app.xml BSPNMobileApp.swf com/bspn/assets/icons -extdir /Users/markusmcgee/Applications/SolsticeConsulting/BSPN_Mobile/BSPNMo bileApp/libs/bin/ane -platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platfor m/Developer/SDKs/iPhoneOS5.1.sdk/
XCode Version 4.3.2 (4E2002)
I'm also using an ad hoc distribution provisioning profile for testing.
I did notice an extreme change in performance using AIR 3.3 Beta but my issue is the same as the original thread. It seems like doing any type of navigator push pop view kills the MouseEvent.CLICK and TouchEvent.TOUCH_TAP event ( have tried both in testing and the result is the same as the vidoes in this thread ).
If you need any more information let me know.
Any word on this issue? I found out avoiding navigator.popView (replaced with a pushView, all views must remember how to open from previous state after gb collection) makes a world of difference in my application. The button lagginess is still there but not as much as before.
Can you please log a bug at https://bugbase.adobe.com and share the bug number with us ?Also please provide a sample application (with sources) which can reproduce the issue .
What was the outcome of this? I had issues with MouseEvent.CLICK. I've switched to TouchEvent.TOUCH_TAP but would like to use GestureEvents instead.
Thus, I believe I need to rely on MouseEvents once again for tapping standard buttons.
Any progress made on this bug? Do we have a bug number?
Didn't file a bug with this.
What I had to do was go back over my code with a fine tooth comb. And
double make sure I went over the best practices and optimization for AIR
Mobile. There are best practices floating around in a power point format
to use. Also, Michael Labriola from Digital Primates did a talk or power
point on what we should be doing in code from an optimization stand point.
All of this helped out a lot and seemed to fix my button press actions. If
I remember correctly my button press actions didn't get resolved until I
played with opaque backgrounds specifically though. This is covered in the
best practices for Adobe AIR for Mobile too.
Hope this helps. If I can think of anything else I will respond to this