|
Viewing 1 to (7 Total) Actuate issues with newest NME |
Total Posts: 15
Joined: May 13, 2012
|
This is my first post here so hello to everyone!
I've recently setup a new pc and installed the latest version of nme which is 3.3.2. The problem I found is that when I build my app for android then the actuate lib is not working properly anymore. The tweens end and the onComplete event is dispatched but the properties of an object don't change. I don't get any errors.
This works fine for flash but seems to fail with android. On my older machine with NME 3.3.0 this works ok both for flash and android. I'm not really sure where the problem lies, whether it's a version problem or I'm just missing something on my new pc.
Tags:
Posted on May 13, 2012 at 6:51 PM
|
|
|
|
Total Posts: 15
Joined: May 13, 2012
|
Re: Actuate issues with newest NME
After countless trials and tribulations it seems that Haxe 2.09 was causing the problem so had to go back to 2.08 which is bad cause I can't use the features/fixes of the newest one. The thing I had to do was not to change the SDK in FlashDevelop to 2.08 but change the path in environmental vars to point to the old Haxe folder. I'm not sure whether changing SDK in FlashDevelop does anything. My problem is now gone, the tweens are working again. I'm just wondering how come no one else reported this issue.
Posted on May 22, 2012 at 1:51 PM
|
Total Posts: 2147
Joined: August 25, 2011
|
Re: Actuate issues with newest NME
This must be something related to the Reflect.setProperty and Reflect.getProperty methods, which were added in Haxe 2.09.
In Flash, getters and setters work just like ordinary properties. Due to the nature of how getters and setters are implemented for various platforms, Haxe reflection would not return getters or setters unless you used the actual name of the getter or setter method.
As a hack/workaround, NME used to use a modified Reflect.hx class for Javascript, that checked for the existence of "jeashGet___" and "jeashSet___" before concluding that a property did not exist on the target. I was happy to remove this hack when Haxe 2.09 was released, but there still may be problems.
Are you tweening a class instance (like a Sprite) or are you tweening a generic object, like { time: 100 }?
Posted on May 22, 2012 at 1:58 PM
|
|
Total Posts: 15
Joined: May 13, 2012
|
Re: Actuate issues with newest NME
I'm tweening a Sprite. Is there a workaround for Android?
Posted on May 22, 2012 at 2:07 PM
|
|
Total Posts: 2147
Joined: August 25, 2011
|
Re: Actuate issues with newest NME
Could you run "haxelib upgrade" and make sure you have the latest version of Actuate?
Posted on May 22, 2012 at 2:16 PM
|
|
Total Posts: 15
Joined: May 13, 2012
|
Re: Actuate issues with newest NME
I have the latest Actuate version 1.40 on three computers. Two of them have haxe 2.08 and the problem was only on the computer with Haxe 2.09. After downgrading to 2.08 all three computers are ok. I compared versions of all libraries/projects aswell as versions of NDK, Android SDK, Ant and Java, the only difference was Haxe version - that's how I got to the conclusion that it has to be the problem and downgrading proved it correct.
Posted on May 22, 2012 at 2:27 PM
|
|
Total Posts: 15
Joined: May 13, 2012
|
Re: Actuate issues with newest NME
I just upgraded to NME 3.4 using 'haxelib upgrade' hoping this will solve my problems but still no luck. Where should I report that issue?
Posted on July 22, 2012 at 6:43 AM
|
