On Mon, 20 Aug 2001, Dominik Vogt wrote:
> On Sun, Aug 19, 2001 at 07:35:15PM -0400, Dan Espen wrote:
> > Dominik Vogt <[EMAIL PROTECTED]> writes:
> > > Dan, I looked at the icon box code in style.c because I wanted to
> > > make it work with changes of the Xinerama state, but the matter is
> > > too complex to write a patch in short time for me.
> > >
> > > What I want to do:
> > >
> > > 1) Default to using the primary screen for icon box specs
> > > (already works for X geometry like specs and is easy to do for
> > > the other syntax).
> > > 2) Recalculate all icon boxes when the Xinerama layout of the
> > > screen changes (switched on or off).
> > >
> > > The difficult part is (2) because all the calculations are done
> > > when the style is defined. The precise spec string is thrown away
> > > afterwards. So doing this requires to remove the calculations
> > > from style.c and do them somewhere is icons.c. Can you take a
> > > look at this, please? I think this could wait until after 2.4.1.
> >
> > Done. You may want to test this on a system that supports
> > Xinerama. I tested it with:
> >
> > Style "*" IconBox -80 240 -1 -1, IconGrid 80 67, \
> > IconBox 1040x20+0-40, IconGrid 80 80, IconFill r t
> >
> > which tests both formats and some negative coordinates.
>
> Great! I am still unsure about a few things that could be done:
>
> - Should each screen have a default icon box?
Yes. The natural way is to place icon on the same screen where
the window is.
> - Should icons always be placed in an icon box that overlaps the
> window's screen first?
Can you please explain what you mean by that?
> - Is it worthwhile to prevent icons from being placed between
> screens if the icon box spans the whole desktop? (I guess not).
Agreed. If the user makes a "global" iconbox, his choice should
be obeyed.
_________________________________________
Dmitry Yu. Bolkhovityanov
[EMAIL PROTECTED]
The Budker Institute of Nuclear Physics
--
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]
