Jump to content
GreenSock

Philip Bulley

Members
  • Posts

    25
  • Joined

  • Last visited

Reputation

1 Newbie

Contact Methods

Profile Information

  • Location
    London, UK
  1. Your commitment to GSAP is amazing. Keep up the great work as always. It's very much appreciated by us devs.
  2. Hey, just wondering if since this post, there is now more of a formalised way to get at this data (other than the two not-so-formal options previously mentioned)?
  3. Totally understand, "regX" and "regY" is certainly sufficient for now. As always, thanks and keep up the amazing work
  4. Thanks Jack. Being new to EaselJS, I wasn't yet aware of regX and regY, that indeed solves my problem Do you think there could still be a benefit in implementing transformOrigin or TransformAroundPoint within the EaselJS plugin? You'd be able to keep your registration point at 0,0 and perform transforms around any co-ordinate without having to compensate when setting x,y position of your DisplayObject.
  5. So I realise that transformOrigin is a CSS property and thus don't expect it to work when tweening scaleX and scaleY of an EaselJS Bitmap, but is there any way I can achieve the same ends? Tweening using a top left origin isn't always ideal. Thanks
  6. I have a tween with a delay of x secs and I want to execute some custom code just before that tween begins. onStart is triggered too late, as that fires just after the tween has started. onInit used to be the solution pre v12, but sadly this seems to have been removed. From http://www.greensock.com/v12/ How can I achieve the same thing with v12? Thanks.
  7. My bad, you were talking about CSS3 transitions in the FAQ as opposed to 3D transforms :)
  8. Simply amazing. As always. Before this version, you stated in the FAQ that the way in which CSS Transforms worked meant that they weren't suitable for a robust animation platform such as TweenMax. Just out of interest, what hurdle did you overcome to make the seemingly impossible, possible?
  9. Sure thing. I can see how that might be seen as an advanced/non-crucial feature in the public API Thanks for considering though.
  10. Do you think it could be a good idea to be able to remove all listeners defined in the vars object without the need to dispose of the loader? I have a situation where I have a root LoaderMax instance (which i never want to dispose of) with several child listeners (childComplete, childProgress), during an initial load, nested loaders will have their events dealt with thanks to those child listeners. Later in the project, I want to be able to unload and load those nested loaders (in this case, when the user toggles HD assets on and off), but I don't want the onChild listeners of the root LoaderMax to fire. Yes, I can remove each listener from the root LoaderMax manually in its complete handler, but it'd be nice to have public access to the following code (from LoaderCore._dump): for (var p:String in _listenerTypes) { if (p in this.vars && this.vars[p] is Function) { this.removeEventListener(_listenerTypes[p], this.vars[p]); } } That way, if LoaderCore is ever updated with new listeners, I don't need to potentially add a new manual removeEventListener. What are your thoughts?
  11. I've PM'd you a new test. It's not an FLA, but an extremely distilled version of how I use the VideoLoaders in my project. I notice the gap about 90% of the time in this example (flash of bright green background). You can re-compile the VideoStandaloneTest.as via MXMLC (I'm using FDT with Flex SDK 4.5.1 targeting FP10.2), but please test the SWF in bin first, just to see if you also get the flicker. Thanks!
  12. So the fix works nicely in the test FLAs I sent you, but doesn't in my main project even when "videoLoader.autoDetachNetStream = false" I'm still getting a couple of frames of black before the video starts playback. After tinkering with VideoLoader, I've found that removing the "if (_video.stage != null)" from VideoLoader._applyPendingPause solves my problem. Kind of. I no longer get the gap, but it would seem that I cannot later dispose(true) of the loader. VideoLoader._dump is getting called with a scrubLevel of 3, but the memory never gets released. The flash player will eventually crash with an "out of memory" trace as I later load more VideoLoaders. I can confirm that when the if statement inside VideoLoader._applyPendingPause is present, the memory is released successfully. Does this help? Anything else you'd like me to try?
  13. Looks good to me. I'll keep an eye on this and let you know if it ever breaks again. Thanks for your, as ever, ultra fast response and fix!
  14. I've put together a test FLA. Basically it seems that the erratic behaviour happens when "videoLoader.autoDetachNetStream = false". If you comment out that line, it seems that all netstreams are attached as expected (but with the gap as explained earlier, so not a viable solution). I'll PM you the link to download the test package. Thanks!
  15. Relieved to see this is something intentional and not a random bug! Apologies for wielding the "BUG" headline!! I have a lot of faith in the greensock toolkit So, I'm now setting autoDetachNetStream on all of my VideoLoader objects, but now it looks like some netStreams are not attached to Video, whereas some are successfully attached (it almost alternates sequentially as I go through videos). I suspect this, as on some videos I see black whilst I can hear the audio. Got to leave work now, but I'll do some more in depth testing tomorrow. If you have any pointers or things you'd like me to test, feel free to let me know Cheers!
×