On Tue, Jan 13, 2004 at 11:31:00AM +0100, Uwe Pross wrote:
> Hi there,
>
> On 13 Jan 2004 at 10:43:24 +0100, Dominik Vogt wrote:
>
> Thanks for that explanation.
>
> > ...
> > * 4. Transients go on the same desk as their parents.
>
> This is the one. :-\
>
> > ...
> > An option controlling this would be in order, but I think it
> > would not help a lot. Normally you do not want popups appear on
> > the current desk when the application is somewhere else.
>
> I see. One should distinguish between transient windows
> which apear automatically e.g. error messages and transient
> windows which were opened by the user e.g. dialog windows.
> But this seems to be a general problem (not of fvwm).
>
> > ...
> > I suggest you exploit either #1 or #2 from the list above. This
> > is probably the easiest:
>
> > Style <annoying window name> StickyAcrossDesks
>
> Well, the window's name is just "Open" or "Save". So not
> very suitable for a special style.
Use FvwmIdent on the window. Maybe it has a suitable class or
resource name. In acroread, the open dialog has the resource
name "OpenDlg".
> As a workaround I disabled
>
> Style * SkipMapping
>
> to see the window at least ;-) For the first time I was
> confused since the window apeared on another desk and the
> viewport did not change.
>
> I used SkipMapping since I got an application which pops up
> small window during compilation to show what it does
> (Compiling, Linking, ...)
Ciao
Dominik ^_^ ^_^
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Jan 13 2004 - 04:53:38 GMT