It actually got so bad today that I started again with a clean image and 
filed-in my classes. In fact, the only reason I'm using 3.7 is because 
of this trouble when I was using 3.6. The problem wasn't even correcting 
itself between squeak-restarts. When you say 'modifier keys' you're 
talking: alt, shift, ctrl, cap-locks etc. correct?  The alt-key theory 
seems unlikely in my case since I don't even think I used that key 
today, but I'll watch for it -- there seems to be a certain mouse 
clicking pattern that precedes this (perhaps?). Thanks Jon.

A related question: is it possible to hand-code ".st" files and then 
just file them in? -- I'm tempted to code within xemacs and then just 
file that code into squeak and try to run it, thus limiting my 
vulnerability to this crazy menu-changing thing (it's not just a menu 
change -- it's effectively a crash.) If this is possible, could someone 
point me to the formatting definition a ".st" must respect? I filed-out 
a sample class and then tried to match the resulting ".st"s format (sort 
of -- i took several liberties) but no success. Specific questions: What 
do the "!" mean? Will squeak mind if I leave out the ^Ms that flood 
these ".st"s? Can I leave out the dates?

All this aside, I'm enjoying smalltalk and squeak.

Chris.


Jon Hylands wrote:

>On Wed, 24 Nov 2004 19:33:32 -0700, Chris Crowley <chris at winterstorm.ca>
>wrote:
>
>  
>
>>Anyone encountered this and 
>>have an insight?
>>    
>>
>
>I have a laptop at work, and sometimes one of the alt keys gets a little
>bit stuck, which can alter the menu behavior in Squeak until I hit it
>again.
>
>You should check your modifier keys carefully the next time this happens --
>give each one a quick jab with your finger and see if that helps.
>
>Later,
>Jon
>
>  
>