state (10/16/2009)
So, this leads into another question.
Why would the Delay be required when moving to 1.0, but worked fine in .08?
This is really tough to say exactly, but the problem could have also just as easily happened in v0.8.x and it would be good idea to add the Delay to your v0.8 code as well.
The error that occurs is because the <Show> Listener is trying to access the field before it's completely (and properly) rendered. The field is not ready at the time the <Show> Listener is fired and a JavaScript error is thrown. This js error stops the remaining components from rendering properly.
What changed between releases?? At the moment I have no idea, but given your original configuration, even the slightest tweak in the internal rendering process might have changed the race condition to swing the other way. Like I said, it would be a good idea to add the Delay to your v0.8 code as well.
Hope this helps.
--
Geoffrey McGill
Coolite Inc.
Development Team
Skype : geoffrey.mcgill
Forum Guidelines | Coolite Examples | Coolite API Docs | ExtJS API Docs | Twitter