I want an alt-tab behaviour like KDE3:

1st) When I press <Alt>+<Tab>, I want a window list that does not move the
     mouse pointer. The mouse pointer is supposed to stay where it is.

2nd) I want to be able to select a window by pressing <Alt>+<Tab> (forward)
     and <Shift>+<Alt>+<Tab> (backward). When I press (<Shift>+)<Alt>+<Tab>
     with one hand and move the mouse with the other hand, then the mouse
     must not interfere with my keyboard action (selecting a window using
     (<Shift>+)<Alt>+<Tab>).

3rd) When I press <Alt>+<Tab>, I optically want to see the windows in this
     list in the order in which they were recently focused, like WindowList
     already does. But: I want the second entry of the list to be selected
     when I open the list with Alt-Tab.

The "CurrentAtEnd" option has the disadvantage that I do not optically see what
I should see (or want to see). It disturbs my perception, because sometimes I
*LOOK* onto the list if I'm searching for something that I do not get at one go.
I have the right order in my mind, but the list shows me something different
when I use the "CurrentAtEnd" option.

It would be a great thing if FVWM were able to fulfill these requirements.
But I'm not sure how could be the right approach to achieve this:

- Make feature requests about creating new options for "WindowList"?

  - There should be an option like "preselectItem n", where I could
    set "n" to "2" to get a better solution than the "CurrentAtEnd"
    option.

  - There should be a "dontmovemouse" option to get a behaviour
    described under 1st).

  - There should be an "ignoremousemovement" option to get a behaviour
    described under 2nd).

- Try to reverse engineer the Alt-Tab behaviour using FvwmIconMan?

  - Trouble is that I need to combine the "Key actions" of FvwmIconMan
    with the "FollowWindowList" option of "FvwmWinList" to get a list
    that does not move the mouse, that ignores mouse movement and that
    selects the second list entry (by using gotobutton or something like
    that)

The bottleneck of my FvwmIconMan approach seems the be able to get a
FollowWindowList behaviour. Does anyone have an idea how to get
such a behaviour? If this means that I have to write a complicated
algorithm then I would do this, but I need a good idea how to start
this way.

How likely is it that somebody enhances "WindowList" with the three
options I described above?

Does anyone has an idea if there could be a better way than my
FvwmIconMan approach?

At first glance, I see these modules:
- WindowList
- FvwmIconMan
- FvwmWinList
- FvwmWindowMenu

Are there more like them that could be worth of thinking about using
or abusing them?

Any ideas are welcome.
Thanks in advance
Michael

Reply via email to