Kai Grossjohann <grossjohann_at_charly.informatik.uni-dortmund.de> writes:
>
> Good morning,
>
> thanks to the new SendToModule command and some GREAT support added to
> FvwmIconMan, I can have the function I most sorely missed from *twm: I
> can now move up and down in the icon manager with the keyboard.
> Here's what I have in my .fvwm2rc file (snarfed right out of the man
> page for FvwmIconMan, modified slightly):
>
> Key j A 3 SendToModule FvwmIconMan sendcommand focus focus + 1 Focus
> Key k A 3 SendToModule FvwmIconMan sendcommand focus focus - 1 Focus
>
> I'm a nasty boy now: I'm still not quite satisfied. When I hit, say,
> Alt-j, the window below the current window in the icon manager is
> given focus. The *twm icon managers allowed me to define one key to
> move among the windows and another to specify one. (Move the
> selection up and down the icon manager -- WITHOUT any window being
> raised or deiconified or anything -- and then hit a special key to
> deiconify, raise and warp to the window currently pointed to.)
>
> Is there anything I can do to achieve the same behavior with
> FvwmIconMan?
>
> Thanks a lot for this feature as it is, though, it's great!
> kai
As you know, there are three ways you can specify a button: abolutely
(like button 4), relative to the focused button, or relative to the
selected button. In the current state of things, when the cursor is
outside of the manager window, there is no selected button, so
you can't use that in your SendToModule command, and that's what you
(and I) would like to be able to do. I left that ouy cause I couldn't
decide which would be better: to remember what the last selected button
was, and use that if none is selected, or start at someweel known place,
like button 0.
The other problem with using the focus button for this is that you can't
give the focus to an iconified window, so any iconified window will
act as a barrier.
I'm probably going to switch to using the syntax that the Next and Prev
commands use, but I still haven't figured out an elegant way to handle
the complications of: specifying the "current" button from which the
command is relative, and specifying the manager as well as the window.
As to the second one, FvwmIconMan is basically a two dimensional window
list, so the simple syntax that Next uses isn't quite sufficient.
So, since you're a consumer, what kinda of behaviour and syntax would
you like?
--
Brady Montz
bradym_at_cs.arizona.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Oct 01 1996 - 16:07:51 BST