>>>>> "Kai" == Kai Grossjohann <grossjoh_at_dusty.informatik.uni-dortmund.de> writes:
Kai> It's been some time since I've looked into AutoRaise under fvwm
Kai> 2.0. From then, I remember that AutoRaise couldn't be enabled on
Kai> a per-window basis, it was all-or-nothing.
That is still the case, I believe.
Kai> Now, I'm a great fan of AutoRaise on a per-window basis, and now
Kai> that AutoRaise is separated into a module, I think I could
Kai> actually implement this myself (including AutoLower, while I'm at
Kai> it). However, I don't know how to do this. In particular, how
Kai> do I make a module that somehow receives enter window and leave
Kai> window notifications including the window id?
Well, fvwm doesn't send that info (focus changes being the closest
thing to that), and I think that it would be just too expensive to
have it send that level of info.
But, I don't see why a module couldn't get the window id's from fvwm,
and check the windows for a style flag (after I make the mods to allow
more styles, that is) or have it's own config info with the window
names/classes (which could be done now, much like how FvwmIconBox was
done at first) that says to auto raise it.
Then, the FvwmAuto module could monitor Enter & Leave notify X events
for those windows itself, rather than get the info from fvwm. Then,
it could send commands to fvwm based on those events.
Check out xev from the X11 distribution (it can take a window id),
since that monitors events like that, for an example.
Kai> Is there any precedent for modules that maintain a per-window
Kai> state during their execution, part of which is determined
Kai> statically on start up (such as: always auto-raise XTerm
Kai> windows), part of which changes during run-time (such as: I want
Kai> this window here to auto-raise from now on)?
I don't think so, but this could be a start. I don't use AutoRaise
myself, but I think it sounds like a good idea and I think people
would like that.
Kai> I'll be grateful for any information regarding already
Kai> implemented features like this, or examples I could look at, or
Kai> documentation I could download.
Well, take a look at xev for starters. I'm sure that adding the event
monitoring stuff to FvwmAuto should be pretty simple for starters.
And take a look at FvwmWinList for how to get the list of windows from
fvwm.
As for adding the additional style options & flags - that's high on my
list for right after the first official distribution of fvwm2.
Speaking of which - does anyone see anything glaring that should be
cleared up before the release?
Chuck
*******************************************************************************
Charles K. Hines
IBM Logic Synthesis developer [BooleDozer (TM)]
Internet e-mail: chuck_hines_at_vnet.ibm.com
IBM Internal e-mail: hines_at_loki.pok.ibm.com (preferred from workstation)
HINESC at FISHKILL (preferred from mainframe)
HINESC at FSHVMFK1 (discouraged, but I'll get it)
*******************************************************************************
"dis ting could have possabiwities if I put my twisted widdle mind to it!"
- Bugs Bunny
"I have a paper plate in my head because they were all out of the metal ones"
- Rick Overton
*******************************************************************************
--
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 Fri Sep 22 1995 - 12:46:36 BST