Thanks for the responses Matt and Sreenivas. For those interested my, work-around for this was to simply remove the exiting slider, and add a replacement at the same place in the child stack (within an VBox). myBox.removeChildAt() and myBox.addChildAt().
One other thing tho - I tried setting this up with a myBox.getChildIndex(myBox.getChildByName()) with no success (also a bug in getChildByName? - assuming name implies id value) instead I simply wrapped the sliders in an VBox to restrict their child order placement to known values. I also noticed a similar issue using state change overrides for things like simple Link items (changing click functionality). Until the next release I've been doing 'state' changes purely programmatically, and when in doubt doing a remove/add child to update my components. Keep on codin' --- In [email protected], Sreenivas R <[EMAIL PROTECTED]> wrote: > > Hi Darin, > > This is a bug. It will be fixed in the next release. > > -Sreenivas. > ------------------------ Yahoo! Groups Sponsor --------------------~--> 1.2 million kids a year are victims of human trafficking. Stop slavery. http://us.click.yahoo.com/WpTY2A/izNLAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
