Now that the furore surrounding modal dialogs has died down I would like to ask
a few questions and maybe make some suggestions for focus handling. I really
like sloppy focus but some applications I use insist on popping up dialogs.
These applications work better with clicktofocus but turning it on for
particular apps is not something I want to do.
Questions:
1) If a module requests to be informed of every window creation what information
gets passed?
2) Is transient_for status available to modules?
3) Is modality status available to modules?
4) If newly created/mapped windows got the focus but sloppyfocus was active
would that quell the complaints of the modality-is-important brigade?
What I'm thinking of is that maybe a module could be written that moves the
focus to newly created windows. I'm pretty sure that it's doable and it would
make applications that pop up dialogs easier to use.
Just focusing on new windows might be too simple so a further refinement may be
to only switch focus if the new window is a transient_for the currently focused
window. E.g. you have an application performing a task and you move to another
apps window, if the first app pops up a window the focus would not switch. This
would be my option but I don't know if the module protocol would be able to pass
enough information.
Real modality might be supportable with a module if modality info could be
passed to modules. On every focus event a check of the windowlist could be done
to see if any transient_for windows have modality on, if one does the focus
could be switched. This would allow modality in a sloppyfocus environment.
Any comments
Tim Phipps.
--
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 Thu Nov 21 1996 - 10:50:07 GMT