Comments for Randy Troppmann

Comment on E4X and namespaces by Darren Moxin

Darren Moxin — Wed, 16 Jun 2010 15:16:29 +0000

Finally! A work around to this very frustrating problem. Thanks for posting this. Does the line:

default xml namespace = timedTextXML.namespace(“”);

…basically remove the name space from the node?

Thanks again,
Darren

Comment on Trackometer: made with AIR for ANDROID by Justin Hills Johnson

Justin Hills Johnson — Mon, 14 Jun 2010 15:43:23 +0000

Great work. I’m glad to hear another developer’s perspective. I can’t wait to try the app.

Comment on Trackometer at Google IO 2010 by Matt

Matt — Fri, 28 May 2010 21:54:30 +0000

Great post and a great app. Looking forward to reading more of your thoughts on Air for Android.

Comment on Trackometer at Google IO 2010 by Tom Ortega

Tom Ortega — Fri, 28 May 2010 21:49:27 +0000

Yeah, when you become all rich and famous, don’t forget the little people like myself. LOL

Congrats on the much deserved recognition for your hard work!

Comment on Double click editable List component by yayo

yayo — Thu, 06 May 2010 13:08:52 +0000

I try to use your code but I ha´ve a problem with ‘selectedIndex’

Comment on RobotLegs, mediators and memory leaks by Randy

Randy — Wed, 05 May 2010 19:58:11 +0000

@shaun Thanks for the link and your twitter response. In my case I just modified my mediator mapping like this:

mediatorMap.mapView(Map, MapMediator, Map, true, false);

so that the creation is automatic but the deletion isn’t. Just a coincidence that the view is a map … as in Yahoo map :-0

Comment on RobotLegs, mediators and memory leaks by Matan Uberstein

Matan Uberstein — Wed, 05 May 2010 19:19:53 +0000

Nice one Shaun!

Comment on RobotLegs, mediators and memory leaks by shaun

shaun — Wed, 05 May 2010 18:51:35 +0000

Dear Anonymous,

Robotlegs is Open Source: you could have filed a bug report or even fixed the code yourself, but you chose to moan.. thanks for the feedback.

Comment on RobotLegs, mediators and memory leaks by shaun

shaun — Wed, 05 May 2010 18:16:20 +0000

With auto-mediation (the default when mapping a mediator) mediators are created and removed automatically as view components arrive on and leave the stage. The mediator is supplied with an EventMap that you can use to wire up your listeners, and when the mediator is removed it’s listeners will be removed along with it. Also, you don’t have to use auto-mediation, you can create, register and remove mediators manually too:

http://knowledge.robotlegs.org/discussions/questions/117-any-other-way-to-create-mediators-other-than-listening-to-added_to_stage#comment_1363130

Comment on RobotLegs, mediators and memory leaks by Anonymous

Anonymous — Wed, 05 May 2010 17:32:50 +0000

Another fun thing about the interaction of robotlegs mediators and states. Its possible for the state change to cause robot legs to create a mediator through the mediator map. This is what you discovered. Whats annoying is that under certain conditions the onRemove can get fired BEFORE the onRegister does. The onRegister function is fired by mapping an event listener to the creation complete event. If the application for some reason starts the mediator then quickly decides to change state again then it will fire that onRemove before your component thats tied to the mediator has a chance to fire creation complete. Drop into the the base class for the mediator map and you can see that the event handler is not removed in the onRemove function…but only once it has fired in the creation complete handler. wheeee!