1 person found this helpful
All it really does is keep things driven by callLater from executing, so
validating properties, measurement and layout of components is blocked.
This allows some effects to move stuff around w/o the layout code fighting
I think resizng the browser now forces a synchronous layout update. Data
service results and failures will not be blocked, but if the results update
a DataGrid, the DataGrid won't show those results until after.
ok so If I understand correctly, If I move around a button with an effect, which doesn't change any sizes and doesn't cause any layout changes of other components, flex will still update those just it case, and setting that property will notify it not to do that until it is forced to - if the effect does changes the layout of other components or some container size. Does what I say makes sense lol ? Sorry your answer was very helpful, I am just trying to make sense why would I use that property on my own and why it's not automatic...
If you move a Button in a Vbox, the Vbox code will try to put the button
back, so blocking validation of Vbox layout is a good thing. But if you
make a Button grow in a Vbox, many times you will want the Vbox layout to
run so the other children shift to make room (and sometimes you won't if you
want to have the growing child to overlap the current siblings). Blocking
validation will not always be the right thing.
Thank you for the helpful answers ! Really appreciated