Not an official publication of Infinite Monkeys, Inc.

FvwmProxy

FvwmProxy is a FVWM2 module that allows the user to locate and control windows obscured by other windows by using small non-overlapping proxy windows.

With a configured key press, the proxy windows are activated. Proxy windows are always on top and try to center on the regular window they proxy. A simple collision algorithm tweaks the positions of the proxy windows to prevent them from overlapping. Pressing the left or right mouse buttons on a proxy window can raise or lower the associated proxied window respectively.

man page

Published versions

FvwmProxy is an officially distributed and supported module of FVWM.

Local versions

List all local versions

Older versions

A prototype version introduced proxy groups.

20060609 ProxyGroup prototype

The larger two Gimp windows are fused and the Python console rides along just on moves.

In this color scheme, blue is iconified and red is pending activation with Meta-Tab.

The ghosted arrow toggles soft inclusion, as seen in the Python console.

v0.9 20021014

20021014 v0.9

fvwmproxy0.91.tar.gz
x86 Linux Binary 20021028

This is compiled for Fvwm 2.5 only.

If you want to play with things that would go in the config file, look at the top of FvwmProxy.c.

You have to add FvwmProxy to the build. Under ./configure.in add "modules/FvwmProxy/Makefile" twice near where it says "modules/FvwmPager/Makefile". Under ./modules/Makefile.am, add FvwmProxy under "SUBDIRS=". Run (or rerun) ./configure to update all the other files.

To use the Alt-Tab switching, try something like:

	Key Tab A M SendToModule FvwmProxy Next

Oddities

If you use Alt-mouse to move/resize windows and you try to grab the window but accidentally hit the proxy, nothing will move. It's a little annoying.

v0.9 20021014

fvwmproxy0.9.tar.gz
x86 Linux Binary 20021014

This is compiled for Fvwm 2.4 only.

Oddities

Under heavy load, I've seen proxies get left on the screen after a new set of proxies pops up during a desk change.

After a few hours, sometimes the module just exits. The log says it received a NULL Fvwm packet. So, I just have start and kill wired into my root menu.

My 'vim -g' has been acting a little odd lately. I'm not sure it's at all related.