Comments on: Databinding to read-only properties in Flex 2

By: pascixqanwaj

pascixqanwaj — Thu, 11 Sep 2008 04:33:33 +0000

nude pics of vanessa hudgens

By: mvegtodiwk

mvegtodiwk — Sun, 23 Dec 2007 16:04:04 +0000

adult friend finder login

By: zodsydnymqo

zodsydnymqo — Fri, 21 Dec 2007 00:22:35 +0000

hot latino chicks

By: ndiqolaljo

ndiqolaljo — Wed, 12 Dec 2007 13:51:35 +0000

nude naked soccer moms

By: Steve

Steve — Mon, 19 Nov 2007 08:44:45 +0000

You can throw an exception from a setter, but that’s a runtime error that you may or may not notice before your product ships. And failing silently, as in your example, might lead to code that’s difficult to debug when you forget that the property was supposed to be read-only.

If you create a read-only property in the way I’ve shown, you’ll get a compile-time error when you try to set that property.

By: Jonathan Buhacoff

Jonathan Buhacoff — Thu, 15 Nov 2007 04:53:49 +0000

Seems to me there’s an easier way:

[Bindable]
public function get myProp():String {
return _myProp;
}
public function set myProp(value:String) {
// do nothing, since the property is publicly read only, or… is it possible to throw exceptions from setters ?
}

private function businessLogic() {
// update _myProp as needed
}

By: Steve

Steve — Tue, 14 Aug 2007 17:16:47 +0000

Actually, with Rasheed’s post the myProp setter function will silently be made public by the Flex compiler, since you can’t have a getter and setter with different scopes. At least, this is what happens in Flex 2 - I haven’t tested this with Flex 2.01 or Flex 3, so your mileage may vary.

By: thomas

thomas — Sun, 25 Feb 2007 17:05:09 +0000

For Rasheed’s post I would guess that reflection during compilation sees only if there exists a “set” and removes the complaint, but would subsequently encounter an access runtime error if it were actually invoked (which doesn’t happen in this example)

By: Rasheed

Rasheed — Sun, 11 Feb 2007 03:55:38 +0000

WARNING: This is nasty, really, but it works and is to my eye more readable and less cluttered.

You can create a read only property that [Bindable] won’t complain about:

[Bindable]
public function get myProp():String {
return _myProp;
}
private function set myProp(value:String) {
_myProp = value;
}

I don’t know why its allowable but it is

By: Rachel maxim

Rachel maxim — Mon, 29 Jan 2007 19:11:14 +0000

Thanks for posting this, I finally have an explanation for why I’m getting this annoying warning…and a solution too! Appreciate it.