search

saviosun / hotween

Automatically exported from code.google.com/p/hotween
0 stars 0 forks source link

HOTween not compatible with Unity Flash export (anyway, Unity is abandoning Flash) #35

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. create 2D Toolkit sprite
2. instal Hotween and Hotween editor
3. add hotween manager
4. in  hotween editor make tween for tk2dSprite, property "Color"
settings: color = red, loop type = yoyo, repeat = -1, duration = 5
5. build & run project to flash
flash export throws errors (look attached unity log)

Original issue reported on code.google.com by Sanguina...@gmail.com on 25 Jul 2012 at 12:35

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Sanguinarity,

thanks for the info. As of now Flash export is not yet compatible with HOTween. 
Mainly because Flash doesn't include some basic libraries that are included 
with all other Unity builds. The Unity guys say they might include them when 
the beta is finished, but they don't know yet, so it's just a matter of waiting 
and see what they do.

Original comment by daniele....@gmail.com on 25 Jul 2012 at 12:41

GoogleCodeExporter commented 8 years ago 
sad...this is really unfortunate cause i really wanted to use HOTween because 
it's so much better then iTween. 

sadly we're definitely targeting flash export. 

will you just be waiting for the flash export to finish?

Original comment by ke...@kixeye.com on 26 Jul 2012 at 1:21

GoogleCodeExporter commented 8 years ago 
Yup, I'm sad about that too, but I'm gonna wait for Flash export to be out of 
beta. Mainly because I need Reflection to emit some fast property/field 
accessors when the tween is created (except than with Transforms), and the 
Unity guys said they will probably allow it in the final Flash release. Without 
that, there is almost no way to be able to animate any property/field of any 
object.

In truth, I found a workaround for that, but it requires a more complex API for 
HOTween users, and an almost complete rewrite of HOTween, so I was planning it 
for HOTween v2 (for which I made some demo tests, but I won't be able to start 
developing it for some months yet).

Original comment by daniele....@gmail.com on 26 Jul 2012 at 10:27

GoogleCodeExporter commented 8 years ago

Original comment by daniele....@gmail.com on 13 Sep 2012 at 11:38

GoogleCodeExporter commented 8 years ago 
The *HOTweenMicro* version of HOTween should now, maybe, work with the latest 
Flash export release. If anyone could try it out and tell me it would be great 
:)

Original comment by daniele....@gmail.com on 7 Oct 2012 at 2:59

GoogleCodeExporter commented 8 years ago 
Just tried HOTweenMicro, get less errors but still this stuff in 
ABSTweenPlugin.as:

Temp/StagingArea/Data/ConvertedDotNetCode/Holoville/HOTween/Plugins/Core/ABSTwee
nPlugin.as(123): col: 199 Error: Type was not found or was not a compile-time 
constant: PropertyInfo.

Temp/StagingArea/Data/ConvertedDotNetCode/Holoville/HOTween/Plugins/Core/ABSTwee
nPlugin.as(123): col: 227 Error: Type was not found or was not a compile-time 
constant: FieldInfo.

Original comment by d...@unit9.com on 1 Nov 2012 at 3:58

GoogleCodeExporter commented 8 years ago 
Thank for trying Dave. I had read that Unity was adding at least some basic 
Reflection, but it seems they still didn't. I'll keep my fingers crossed for 
the future.

Original comment by daniele....@gmail.com on 1 Nov 2012 at 5:38

GoogleCodeExporter commented 8 years ago 
Are there any work arounds for this? I really want to use HOTween instead of 
GOKit or iTween (used all 3 and HOTween is the best by far) but the Flash 
support is killing me =(

Like, instead of using reflection could we just have a list of hardcoded 
supported properties and how to access them?

Original comment by tst...@gmail.com on 18 Dec 2012 at 7:54

GoogleCodeExporter commented 8 years ago 
Sadly, the only way to avoid Reflection would be to restrict the properties 
that can be animated to hardcoded known properties, as you mentioned. But that 
would nullify the flexibility of HOTween and make it into another engine. 
Actually, when animating Transforms and some other things, Reflection is 
already avoided, but to generate a fast getter/setter for unknown properties 
there is no other way (or better, there is another way, via lambdas, which was 
suggested by stfx, and which I was thinking of implementing in HOTween V2, but 
it requires more experience from the users, and I'm not sure it would work with 
Flash either).

I asked the Unity guys if they'll implement basic Reflection soon, since they 
initially said they would, but had no answer as of now. I really think they 
will, sooner or later, because Flash itself uses Reflection a lot.

That said, I will make some test to see if I can quickly implement an alternate 
version of HOTween, which will work with lambdas instead than Reflection.

Original comment by daniele....@gmail.com on 19 Dec 2012 at 4:08

GoogleCodeExporter commented 8 years ago 
Understood. After trying out the other tweening libraries and realizing that 
only a hacked up version of iTween runs on Flash I decided to punt on this and 
just cross my fingers that Unity starts supporting Reflection soon.

Original comment by tst...@gmail.com on 19 Dec 2012 at 6:25

GoogleCodeExporter commented 8 years ago 
Important note: HOTween won't even try to be Flash compatible anymore, since 
Unity abandoned Flash export (and I can totally understand them, since Adobe 
took a wonderful engine developed by Macromedia and completely wrecked it 
thanks to bad choices and an evident "I don't know what to do with it" attitude 
- and I'm really sad for this, since I use Flash professionally since more than 
a decade). Read Unity's official blog for more infos: 
http://blogs.unity3d.com/2013/04/23/sunsetting-flash/

Original comment by daniele....@gmail.com on 24 Apr 2013 at 9:55