On 21-01-2014, at 5:29 PM, Chris Muller <asqueaker at gmail.com> wrote:

>> How is what you want different than simply selecting the "Changes"
>> button on the MC browser?
> 
> Answering my own question, "because I might be in the History browser
> and that should work."  NP, it should be there..
> 
> But this blow up isn't obvious to me and something suggests a timing
> issue that might be the sign of a bug exposed, than created.
> 
> Putting
> 
>      100 milliSeconds asDelay wait.
> 
> at the top of MCVersionHistoryBrowser>>#getMenu: avoids blow up.
> Something causing the #selectedInfo to not be there immediately -- so
> maybe this is related to the pre-selection thingy?  

Sounds like the work triggered by selecting the list entry is taking a ‘long time’ (by some definition) and the pre-select is therefore in a state not able to cater for a menu selection. The question likely to need answering is why it takes so long to do the list selection work. So far as I can make out from the code it should be pretty fast.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Oxymorons: Living dead