El dom., 1 de nov. de 2020 a la(s) 23:47, claudio canepa ([email protected]) escribió:
> There you can see an inspiration for a possible workaround: look at class > MoveByAdditive, if you write a JumpAdditive then it can compose with another > additive or instant action as you described, > > Not ideal but the most immediate solution. > > > Long term, maybe a new action operation over Actions could be defined > worker_action = actor.do(Jump(...)) > actor.do(Modify( worker_action, fn_my_action_patcher) > > where Modify should extract init params from the worker action, calculate > remaining_duration, call the user provided fn_my_action_patcher with those > params, the fn must return the desired composition. > > Looks not easy to use, but maybe some experimentation can produce something > viable. Wonderful, thanks! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org.ar/ Twitter: @facundobatista -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/cocos-discuss/CAM09pzQ4xeoEMYsqkNuLhFUdfeAojj9PcX1gG4NUu%3Dtz6i1upQ%40mail.gmail.com.
