Comments on: [Bindable] on a read-only getter is unnecessary and will be ignored. http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/ Just another WordPress site Tue, 31 Jan 2012 13:51:35 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Tim John http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-10815 Tim John Fri, 03 Jun 2011 09:44:14 +0000 http://joshblog.net/?p=656#comment-10815 @seanos I tried the method you suggested, having the getter as public and the setter as protected/private, but it seems that the setter's namespace is overridden to public. As a result, the property isn't read-only and I can change it from outside the class. Here's a good example of how to truly <a href="http://www.rubenswieringa.com/blog/binding-read-only-accessors-in-flex/comment-page-8#comment-122896" rel="nofollow">bind to a read-only getter</a>. @seanos I tried the method you suggested, having the getter as public and the setter as protected/private, but it seems that the setter’s namespace is overridden to public. As a result, the property isn’t read-only and I can change it from outside the class.

Here’s a good example of how to truly bind to a read-only getter.

]]> By: seanos http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-1902 seanos Fri, 24 Jul 2009 09:53:01 +0000 http://joshblog.net/?p=656#comment-1902 To get around this problem I created a setter, but set it private. From an external class this property is still 'read-only', but the event does get fired implicitly by the [bindable] private setter function To get around this problem I created a setter, but set it private. From an external class this property is still ‘read-only’, but the event does get fired implicitly by the [bindable] private setter function

]]> By: Tink http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-1901 Tink Thu, 23 Jul 2009 08:52:56 +0000 http://joshblog.net/?p=656#comment-1901 I'm with Josh. Everything you mark bindable should have a custom event that's fired when the property changes. I’m with Josh.

Everything you mark bindable should have a custom event that’s fired when the property changes.

]]> By: evden eve http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-1900 evden eve Sat, 18 Jul 2009 15:29:53 +0000 http://joshblog.net/?p=656#comment-1900 good works good works

]]> By: Josh McDonald http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-1899 Josh McDonald Thu, 16 Jul 2009 07:32:28 +0000 http://joshblog.net/?p=656#comment-1899 Not only does using a custom event name per property improve performance, it makes it trivial to add some [Event] metadata to your class or MXML document, and then you can trigger off property changes easily using events, without using the MXML binding synax or going through BindingUtil. Not only does using a custom event name per property improve performance, it makes it trivial to add some [Event] metadata to your class or MXML document, and then you can trigger off property changes easily using events, without using the MXML binding synax or going through BindingUtil.

]]> By: [Bindable] on a read-only getter is unnecessary and will be ignored. – Josh Talks Flash | Enigmatic Thought http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/#comment-1898 [Bindable] on a read-only getter is unnecessary and will be ignored. – Josh Talks Flash | Enigmatic Thought Thu, 16 Jul 2009 02:01:02 +0000 http://joshblog.net/?p=656#comment-1898 [...] Josh Talks Flash Josh posted about something I just ran into the other day.  The warning [Bindable] on a read-only getter is unnecessary and will be ignored appeared when I was creating a Model for an MVC application.  Since I was using an ArrayCollection [...] [...] Josh Talks Flash Josh posted about something I just ran into the other day.  The warning [Bindable] on a read-only getter is unnecessary and will be ignored appeared when I was creating a Model for an MVC application.  Since I was using an ArrayCollection [...]

]]>