It is. I've mentioned that problem before. Having moaned though, I'd like to _keep_ preselection and have it just _work_. On a slow machine (my laptop) it provides valuable UI feedback. On a fast machine you'd see the value by opening up a Dependency Browser and clicking around the packages.

frank

On 16 Sep 2013, at 23:33, Chris Muller <asqueaker at gmail.com> wrote:

>> sometimes by changing list selection with vertical arrow keys
> 
> I haven't been experiencing many yellow-crosses-of-death but I have
> noticed that arrowing down through lists by holding down-arrow key now
> has a problem where the selection will jump back up every few
> milliseconds.
> 
> Easy to reproduce.  Just hold down-arrow in any list.
> 
> I'm pretty sure this has to do with the recent feature of
> "pre-selecting" the selection that Tim wanted.
> 
> 
> 
>> - navigating in debugger stack similarly...
>> For this specific stack, I just can't remember, too many occurrences...
>> 
>> 
>> 2013/9/17 Bob Arning <arning315 at comcast.net>
>>> 
>>> Well,
>>> 
>>> - your stack is truncated, is there more somewhere?
>>> - can you say anything about how you got there?
>>> - did you notice that lines was not nil by the time the stack was written:
>>> 
>>>        lines:     {a TextLine 1 to: 67 . a TextLine 68 to: 139 . a
>>> TextLine 140 to: 240 . ...etc...
>>> 
>>> Cheers,
>>> Bob
>>> 
>>> On 9/16/13 5:26 PM, Nicolas Cellier wrote:
>>> 
>>> Lately I have many instances of these yellow cross over red background
>>> that happens when a low level morphic error is encountered.
>>> 
>>> It seems related to a MultiNewParagraph lines being nil like in following
>>> stack example.
>>> 
>>> I don't know if it can help a morphic guru, but I just hate those stateful
>>> behavior with volatile states...
>>> 
>>> Really hard to debug/understand!!!
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>