On Thu, 16 Aug 2001, Dominik Vogt wrote:
> On Wed, Aug 15, 2001 at 08:30:20PM +0700, Dmitry Yu. Bolkhovityanov wrote:
> >
> > I've added an optional "global" switch, which means that
> > maximization should be made on a global screen, otherwise it is made on
> > the screen where the center of a window is. "grow*" are also adjusted
> > (that turned to be the easiest part of the task).
>
> I have been thinking about an entirely different approach that
> uses XGeometry specs:
>
> Maximize on [EMAIL PROTECTED]
>
> The problem here is to specify the resize unit (screen % or
> pixels) and where to place the "grow" option. The same syntax
> could be used for the Move, Resize and ResizeMove commands.
IMHO these two approaches aren't contradictory -- yours allows
more flexibility, while the logic im my patch is required in case when no
parameters are specified (i.e. just "Maximize") or the old syntax is used
(incl. e.g. "grow"). But, of course, with some efforts old syntax parser
can be changed to generate an appropriate "on" geometry spec.
There's a pitfall in geometry syntax for Maximize: what would
mean "Maximize [EMAIL PROTECTED]" if applied to a window on different page/desk?
Would it be current screen where the *pointer* is, or the screen, where
that *window* is (more precisely, where it *would* be when "Focus"
applied)? And what to do in case when current page doesn't start on a
page boundary?
_________________________________________
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]
