Good to know. And it does make sense as described in the comments. This is for my future reference and for others who may experience it.
In a nutshell, if you have a getter/setter pair and make them [Bindable], the setter will not execute again if the new incoming value is the same as the current value. That speeds up performance but if you always need to check that value, it might be a bit confusing why it’s not executing.
nwebb » One Reason Why Your Flex Getter May Not Execute
Cause
As soon as you make the getter/setter bindable, Flex stops running the setter whenever the value you’re sending in already matches the value that the corresponding getter will return.
Solution
The solution (or at least one solution) is not to rely upon the default propertyChange event which is dispatched for bindable values, and instead create/dispatch a custom event
So for this particular Flash AS3 project I am doing that uses Flex as the code editor, I was just about to write a getter/setter pair and thought “perhaps someone has made a way to automate this…”
Quick Google later…
No More Writing Getters and Setters in Flex
eokyere blog has one of the best Flex productivity tips I have seen in quite a while. I build AS3 components all day, and spend way too much time manually typing getter and setter methods. Using the Dash plugin for Eclipse and eokyere’s productivity with with dash in eclipse, you’ll never write another getter and setter again!
A nice template for Flex for incorporating SWFObject, history, and deep linking.
Just Flex: Swfobject 2.1 Flex template. HistoryManager and DeepLinking supported as well
I have been using Geoff Stearns’ SWFObject for a long time. I think it will be useful to share my index.template.html that tuned for using with SWFObject 2 2.1. I was inspired with Ted Patrick’s FXWidget project that uses SWFObject 1.5 for embedding flex content to html page. So now it supports HistoryManager and DeepLinking.
Just want to keep a reference to this one
Tyler Egeto
I’ll be releasing more tools and helpers in the near future as I formalize / clean-up my existing code libraries. In addition to the ActionScript pagination system released earlier this month, PaginatorAS3, today I’m release a small Tooltip system.
I haven’t had to use this yet but it’s definitely a gotcha to keep in mind if doing deep copies and things aren’t working exactly right…
On [Transient], ObjectUtil.copy(), and Casting – darron schall
I ran into an interesting situation not too long ago where ObjectUtil.copy wasn’t working quite as I had expected. The solution that I came up with was to rely on [Transient] metadata. Confused? Let me explain…
Going to try to get back into blogging… again…! It’s just been super busy which is a good thing all things considered.
After learning a neat little shortcut on copying objects using a byte array, there was a link to this for duplicating DisplayObjects. Quite useful.
kirupaForum – View Single Post – ActionScript 3 Tip of the Day
ActionScript 3 no longer has a duplicateMovieClip method for MovieClip instances (or any DisplayObject instances). Instead, it’s suggested that you just create a new instance of the display object you wish to duplicate using its constructor. This, however, is not the same as duplicateMovieClip, and, really, is more like using AS1 and AS2’s attachMovieClip. For a more accurate representation of duplicateMovieClip in AS3, consider the following function…
RSS - Posts