On 17 Oct 2002 12:47:14 -0700, Tim Freedom wrote: > > Another thing to note, why is it that transients are always above > other windows beyond their initial bring-up state. In other words, > I have this "Open Page" Window which when comes up flickers :-) and > then gets focus and I can type into it no matter where my cursor > was -- which is cool. But assume I want to paste-in something that > was on its parent window, if I move the mouse (and I use MouseFocus) > to purposely lose the focus on the transient, the transient resists > being lowered. If I force a "lower yourself" command on it, the > parent gets lowered as well - is this intended behavior ? Does anyone > else see it a bit too forceful and harsh ? I would have thought that > the 'GrabFocusTransient' just grabs the focus and raises itself > upon bring-up. Ideally, the transient should be at least "forcible" > to be lowered if one opted to do it via a 'lower' command, no ?
If you search for "Transient" in the man page you may find some insights. The default is: Style * RaiseTransient, LowerTransient, StackTransientParent I use: Style * DontRaiseTransient, DontLowerTransient, DontStackTransientParent > Last suggestion :-) it would really be cool to have an automatic > mechanism to get all the necessary data that you as developers need > to see to report a bug (or an oddity). Something akin to emacs' > "report-emacs-bug" or emacs VM's "vm-submit-bug-report" which pretty > much dumps the configuration options, and various internal important > state values/settings. A builtin command (or an external script via > perl or something) could be invoked via a menu entry which would result > in a window (similar to FvwmIdent's output) which one can cut-n-paste. > Map that "fvwm-report-bug" in the source (like Alt-Tab is done today) > to say Alt-F12 and its available to all fvwm users. We already have fvwm-bug (should be in your $PATH). Copying from FvwmIdent would be nice, but it does not contain much more information than xwininfo -all (that may be copied). FvwmCommand(1) provide more like an information you speak about, but it is inconvenient to use and I will remove this functionality sometimes anyway as Dominik requested. I will think about something more convenient for dumping style and other information about a window, but this will be of limited use and really not something to be added to fvwm-bug by default. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
