Hi Jeffry, *Why wouldn't you just call commitProperties() directly?*
commitProperties() is a protected method. The OP stated that he is working with *some UIComponent *and that he changed public properties such as *includeInLayout= false *and *selectedItem**. *I took this to mean he is asking how to manipulate the component's state using the component's public interface. If he is going to create a subclass of UIComponent and add state logic internally, he may as well call commitProperties() directly within the component. On Wed, Mar 11, 2015 at 9:16 PM, Jeffry Houser <jef...@dot-com-it.com> wrote: > On 3/11/2015 10:38 PM, Jake Knerr wrote: > > To the OP: if you don't want to extend the component, you should be able > to get commitProperties() to fire on a component that has not been added to > the displayList by first calling invalidateProperties() and then call > validateProperties(). > > *E.G.* > var cmp:UIComponent = new UIComponent(); > cmp.invalidateProperties(); > cmp.validateProperties(); > > For the above example, cmp's commitProperties() method will fire even > though the component isn't on the displayList. > Both invalidateProperties() and validateProperties() are required. > > > Why wouldn't you just call commitProperties() directly? > > -- > Jeffry Houser > Technical Entrepreneurhttp://www.jeffryhouser.com203-379-0773 > > -- Jake Knerr - Flex Developer Ardisia Labs www.ardisialabs.com
