On Fri, Apr 30, 2010 at 11:20:34AM -0400, Shriver, Daniel wrote:
> I've tried what you gave above (except with no ", PositionPlacement x y"
> on the second line), and with the two lines in reversed order (possibly a
> misinterpretation of your "sort out the ordering" comment given below),
> again with no PositionPlacement. Neither seem to give the results I'm
> after.
They wouldn't do. What I was referring to here in terms of order, isn't the
order that your style lines are listed in [1], but the order these two windows
are actually created in. Now, there's no real guarantee that if you just
did this:
DestroyFunc StartFunction
AddToFunc StartFunction
+ I Exec exec bottom_window
+ I Exec exec top_window
That bottom_window would load before top_window. Because I was assuming the
order did matter, you would have to enforce synchronousness by way of:
DestroyFunc StartFunction
AddToFunc StartFunction
+ I Exec exec bottom_window
+ I Wait bottom_window
+ I Exec exec top_window
... but in your case, this no longer applies because of what you've already
told me. Hopefully I've inferred you correctly?
> I'm confused about "PositionPlacement", I thought that just puts the GUI
> widget on a given spot on the virtual desktop, not sure why it would help.
> The tiny widget (which we never want to have keyboard focus) can be moved
> all over the screen by the user.
See my other reply about this.
> 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. Some people have a rather buckshot approach at
blindly setting it for any Java programs. Given you've never heard of it --
and that the default is *not* to use Lenience as a style option, you don't
need to worry. It were more a case of if you had set it, to not do so for
this bottom_window.
-- Thomas Adam
[1] Although this order does matter in most situations, thankfully it's out
of scope here.
