I think normally if changing property1 also calls for a change in property2, that change should happen in the setter for property1. Then both properties get "committed" in commitProperties()
If your situation is special and you can't follow that pattern, you can try a callLater() on invalidateProperties() On 5/27/09, reflexactions <reflexacti...@yahoo.com> wrote: > It seems that if during the validateProperties call,l I change some random > properties and one of them calls invalidateProperties() in order to complete > processing during the next commmitProperties() phase, the commitProperties > never runs. > This is because at the end of processing the initial validateProperties the > invalidation flag is cleared so blocking the next commitProperties from > running. > > Is that right and how to work around it for general properties. > > > tks > > > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Alternative FAQ location: > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links > > > > -- Sent from my mobile device
