x servers relationship with FVWM

Hi all,

I have a simple question:

When an XEvent is generated from the keyboard, what is the path it follows from there to actually being displayed on the screen? my understanding is the following:

device -> Xserver -> FVWM -> Xserver -> Application (xterm, etc).

Could someone let me know if I am correct or not?

thanks,
Skender

Jared,

I know we’ve covered this in the past.

device ->Xserver -> FVWM --> Application

FVWM will ultimately intercept all XEvents, since that’s the one client that’s greedy. If the XEvent is not for the specifc use of the WM, then it propogates itself down to the underlying application, else ultimately does nothing.

HTH,

– Thomas Adam

If the XEvent is not for the specifc use of the WM, then it propogates itself down to the underlying application, else ultimately does nothing.

This was the part that I was a little fuzzy on - for some reason, I was under the impression that after FVWM had looked at an XEvent, the XEvent returned to the X server and then was propogated onto the target app - thanks for clarifying that for me.

As always, thanks,
Skender