spontaneous menu change

Bert Freudenberg bert at impara.de
Thu Nov 25 16:01:13 UTC 2004


We just tried on Mac OS X and Windows, and could not replicate the 
problem. Judging from your EMail-Clients both of you are using Linux. 
So I strongly suspect it's a problem in that VM. Bug Ian about it ;-)

- Bert -

Am 25.11.2004 um 11:34 schrieb Chris Crowley:

> that's it exactly and hitting the Caps Lock key solved it the last 
> time this occurred.
>
> Chris.
>
>
> Milan Zimmermann wrote:
>
>> There is something preventing the menu from working, that is probably 
>> not a feature:
>>
>> When your Caps Lock is "on", the Left-Button click no longer works - 
>> nothing is "clickable" .. in fact clicking on a menu item exhibits 
>> itself as mere change in the display (small image attached), but no 
>> action.
>>
>> Not sure this has anything to do with what you are experiencing,
>>
>> Milan
>>
>> On November 24, 2004 09:33 pm, Chris Crowley wrote:
>>
>>> Hello:
>>>
>>> I'm using squeak3.7 (this issue happened w/ 3.6 as well.)
>>>
>>> I'm using a workspace window to test code: I type in the workspace,
>>> select the code I typed, and then click on the middle/wheel mouse
>>> 'button' and choose "copy", "paste", "do it", "print it" etc. from 
>>> the
>>> usual menu that pops up in this context. Every so often however (at
>>> least once a coding session), the usual menu doesn't pop up, rather 
>>> the
>>> 2nd page of this menu pops up, and there's no way to get back to the 
>>> 1st
>>> page, since nothing is selectable. When this happens, the world menu
>>> changes as well, and nothing is selectable from it either. After a
>>> while, this "bug" corrects itself or I inadvertently do something 
>>> that
>>> corrects it. For instance, I went away from squeak and typed this, 
>>> came
>>> back, and the usual "do it" "print it" etc. menu popped up just fine.
>>> The next time it happened I went away to continue this email, 
>>> returned
>>> to squeak, and the problem hadn't healed itself. But on returning to
>>> squeak a minute later it was fine again. Anyone encountered this and
>>> have an insight?
>>>
>>> Chris.
>




More information about the Squeak-dev mailing list