Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

Philip Bulley

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Newbie

About Philip Bulley

  • Rank

Contact Methods

Profile Information

  • Location
    London, UK
  1. 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)?
  2. Totally understand, "regX" and "regY" is certainly sufficient for now. As always, thanks and keep up the amazing work
  3. 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.
  4. 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
  5. 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.
  6. Sure thing. I can see how that might be seen as an advanced/non-crucial feature in the public API Thanks for considering though.
  7. 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 Loa
  8. 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!
  9. 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
  10. 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!
  11. 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!
  12. 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 m
  13. I'm only using the word bug here as something that works with LoaderCore.version: 1.83 no longer works the same way with LoaderCore.version: 1.87. I have two H.264 video files, the end of the 1st cuts seamlessly to the beginning of the 2nd. When the first video dispatches VIDEO_COMPLETE, I do the following: removeChild( video1.content ); addChild( video2.content ); video2.gotoVideoTime( 0, true ); After swapping versions of greensock.swc, I noticed that 1.87 will display a couple of frames of black whereas the older 1.83 will seamlessly swap between the two videos, so 1.83
  14. I was thinking that maybe the easiest way to do this would be for XMLLoader.parseLoaders to actually add the auto generated name attribute (ie. loader23) to any activated XMLNode (, , , etc). Then I could call: LoaderMax.getLoader( myXML..scene.( @id == 'train' )[0].assetList[0].LoaderMax.( @bandwidth="high" )[0].@name )
  15. Hey Jack, I've found myself in a situation a couple of times now where it'd be great to be able to getLoader by the XMLNode which declared it. What do you think about being able to do something like the following: // AS3 LoaderMax.getLoader( myXML..scene.( @id == 'train' )[0].assetList[0].LoaderMax.( @bandwidth="high" )[0] ) // Here's the XML Here, I'm using simply to group files (so no url present), and would prefer not to give them and subsequently manage name attributes, as in this case they're better identified by being children of scene.( @id == 'trai