On Tue, May 04, 2010 at 07:24:10AM -0400, Shriver, Daniel wrote:
> > but the order these two windows are actually created in. ...
> >
> > DestroyFunc StartFunction
> > AddToFunc StartFunction
> > + I Exec exec bottom_window
> > + I Exec exec top_window
>
>
> Does it matter if fvwm doesn't create the windows? We have one
In the above example, no. And note that, FVWM isn't "creating the windows"
-- the application you're running has to do that.
> application launch a suite of applications, and that one app does time
> synching as well as monitoring. I think we might have a way to stagger
> the launch (typically we start them up nearly simultaneous with no
> guaranteed order and when they all signal they are "ready" we start the
> suite)
That's OK.
> > ... but in your case, this no longer applies because of what you've
> > already told me. Hopefully I've inferred you correctly?
>
> I don't understand.
>
> > > You mentioned that the Java app should not have lenience set. Is that
> > > a java-swing setting, or something in the fvwm config file.
> >
> > It's a FVWM setting which would force focus on Java windows which would
> > otherwise not accept it.
>
> I'll double check my config file for it.
It won't be there, most likely. :)
> ----------------------------------------------------------------- I'll
> include (below) some questions from your earlier email. I'd thought about
> sending it, I was hesitant about pestering the group though. I seem to be
> having a hard time wrapping my head around the fvwm way of doing things.
> I've played around with it but tend to lock up my display:
> -----------------------------------------------------------------
Then you're going to need to send me your config, since this won't lock the
display up -- it's something else.
> Is there some way I can get fvwm to tell me what file it uses "normally"
> (without the -f directive)? The directory structure isn't quite the same
> as what is documented on the net and I'm thinking I should be copying (and
> editing the copy of) a different fvwm config file.
It's clear from the manpage:
$HOME/.fvwm/config
/usr/local/share/fvwm/config
$HOME/.fvwm/.fvwm2rc
$HOME/.fvwm2rc
/usr/local/share/fvwm/.fvwm2rc
/usr/local/share/fvwm/system.fvwm2rc
/etc/system.fvwm2rc
Note that, FVWM will only process the *FIRST* file it finds in the list
above, *IN THE ORDER* listed above. And note again, that
"/usr/local/share/fvwm" should be checked against the output from:
"$(fvwm-config -d)" -- as it may well be different on your system.
Yes, you may contact me off-list. I don't make a habit of it, but be aware
I will likely forward any relevant emails back to this list for archive
purposes.
-- Thomas Adam
