John,

Could it be that something somewhere remembers the shift key
condition when you switch to console mode, and restores it when
you return?

That would be a heck of a bug, but everything is possible I guess.

Personally I get the feeling that the "key up" message sometimes just
doesn't pass the boundary between the switching from full-screen CLI to the
GUI, and the "key down" state simply stays active there, only to bother me
when I switch back to it.

Though I can't think how you'd switch to console mode with the
shift key down.

... and I only realized this only much further down the road :-\ :-)

I've been wondering about that too. But I realized that many other keys
could be remembered in their pressed position, but just not have any averse
effect -- other than having to, if it happens, press the key twice to have
it appear. Hmmm ...

Not that it solves the problem, but it might narrow down where
to look!

If you have any idea, don't hesitate to mention it ! From my POV it could
be anywhere between the computers keyboard-communication chip (I'm using a
PS2 keyboard) and the very application that is absorbing the keystrokes.

Interesting; IME, any lack of detection of a PS/2 _mouse_ isn't
usually restored by plugging it in again

No, but I imagine that the keyboard could be sending, when power is aplied,
a "waking up" sequence, which a driver could be using to initialise/reset
its own state.

Regards,
Rudy Wieser


-- Origional message:
J. P. Gilliver (John) schreef in berichtnieuws
...
In message , R.Wieser
writes:
Lee,

In order for an otherwise innocent double click to invoke several files
at once one normally has to have been in that folder before and single
clicked on an object which highlights it.

There you mention something. Only now I realize that if the selection
would
be done from the first item I should have been seeing a lot of open
folders -- which I don't. I have to check that next time it happens.

But yes, the folder I'm double-clicking an item in was already open
before I
switched to-and-back-from the console window.

A thought: the behaviour is as if you had the shift key held down (so it
activates several files when you only wanted one), yes? Could it be that
something somewhere remembers the shift key condition when you switch to
console mode, and restores it when you return? Though I can't think how
you'd switch to console mode with the shift key down. But a possibility
to ponder. Not that it solves the problem, but it might narrow down
where to look!
[]
And I'm not really sure I am talking about the same thing you are. Yet.

I get the feeling we now are. By the way, thank you for *not* biting my
head of when I mentioned we weren't (I've got experiences otherwise ...
:-\ ).

I know what you mean. Nice to find civilized discourse for a change
(I've read on in the thread). We old hands perhaps remember politer
(and/or perhaps just more patient) times ...
[]
You use a PS2 keyboard I assume?

Yep. One of the last ones in existence it seems. :-)

It does, sometimes, doesn't it! (I always prefer to use PS2 - not only
because it works from boot which USB often don't, but because it doesn't
use up a USB socket, instead using a socket which would otherwise not be
being used at all. Though I gather some motherboards - and certainly all
laptops for quite a few years - no longer necessarily _have_ PS/2
sockets.)
[]
By the way: yesterday it happened again. This time I did not touch my
keyboard, but physically dis- and reconnected it again. The sticky key
was
no more.

Interesting; IME, any lack of detection of a PS/2 _mouse_ isn't usually
restored by plugging it in again (USB ones _do_ re-detect); I don't
think I've tried it with a keyboard.

In other words: it does not seem to be a physical problem (might still be
in
the keyboards electronics, but as the moment of appearing seems to be
bound
to what I do in the OS I doubt that).
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

As the man said when confronted by a large dinner salad, "This isn't food.
This is what food eats."