Re: bug with X window focus switching?

Thread View: gnu.epoch.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by rodrigo vanegas Mon, 09 Nov 1992 19:58

#352

Author: rodrigo vanegas
Date: Mon, 09 Nov 1992 19:58

27 lines
1569 bytes

>The original intent of the filled cursor was to let you know where the
>focus was. However, no focus events are sent to either emacs or xterm.
>
>The twm icon manager is the one handling the decorations, so it knows
>that it wants to see the window corresponding to the icon manager
>entry to be highlighted. You may consider this a bug in twm if you
>wish, but emacs, epoch, and xterm all have no knowledge of how the
>events are reaching it when it is not currently the window in 'focus'.

I think you've misunderstood my report.  I find that xterm and emacs
*are* aware of the change of focus and reflect this awareness by
having filled or hollow cursors.  Epoch, too, is aware of focus
changes when they occur in by the more direct movement of the mouse
from one region of the screen to another.

Unlike emacs and xterm and a number of other apps where this is
relevant, epoch is not aware of focus changes when they occur as a
result of keyboard input.  I don't know exactly whose fault it is or
what the deal is exactly.  But i do know that emacs and xterm handle
this event appropriately. 

Epoch is the problem this time -- not twm.



rodrigo

Re: bug with X window focus switching?

#354

Author: Jeroen van Maanen
Date: Tue, 10 Nov 1992 16:21

27 lines
1321 bytes

rv@cs.brown.edu (rodrigo vanegas) writes:

[stuff deleted]

>I think you've misunderstood my report.  I find that xterm and emacs
>*are* aware of the change of focus and reflect this awareness by
>having filled or hollow cursors.  Epoch, too, is aware of focus
>changes when they occur in by the more direct movement of the mouse
>from one region of the screen to another.

>Unlike emacs and xterm and a number of other apps where this is
>relevant, epoch is not aware of focus changes when they occur as a
>result of keyboard input.  I don't know exactly whose fault it is or
>what the deal is exactly.  But i do know that emacs and xterm handle
>this event appropriately. 

I can confirm this (I noticed it only the day before yesterday myself)
Epoch doesn't change the state of the cursor where xterm does as the
result of a keypress event. Not that it's too much of a problem though.

--Jeroen

>Epoch is the problem this time -- not twm.



>rodrigo

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads