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/ Josh Tynjala explores Flash, Flex, and ActionScript. Thu, 11 Mar 2010 19:18:42 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: seanos http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/comment-page-1/#comment-61186 seanos Fri, 24 Jul 2009 09:53:01 +0000 http://joshblog.net/?p=656#comment-61186 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-page-1/#comment-61170 Tink Thu, 23 Jul 2009 08:52:56 +0000 http://joshblog.net/?p=656#comment-61170 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-page-1/#comment-61145 evden eve Sat, 18 Jul 2009 15:29:53 +0000 http://joshblog.net/?p=656#comment-61145 good works good works

]]> By: Josh McDonald http://joshblog.net/2009/07/15/flex-readonly-bindable-getter-ignored-warning-explained/comment-page-1/#comment-61126 Josh McDonald Thu, 16 Jul 2009 07:32:28 +0000 http://joshblog.net/?p=656#comment-61126 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-page-1/#comment-61123 [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-61123 [...] 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 [...]

]]>