Re: FVWM: mfvwm

From: Mikhael Goikhman <migo_at_homemail.com>
Date: Fri, 14 May 2004 02:03:20 +0000

On 13 May 2004 21:25:29 -0400, Phil Stracchino wrote:
>
> On Thu, May 13, 2004 at 05:36:01PM -0400, Dan Espen wrote:
> > Phil Stracchino <alaric_at_caerllewys.net> writes:
> > > Simple question:
> > > Can a vector button have multiple vectors on it? (I'd like to create a
> > > vector button with multiple raised areas.)
> > > If so, how?
> > > If not, I guess I'll have to work around it with a long serpentine
> > > polyline, or perhaps a bitmap.
> >
> > Have you been here:
> >
> > http://www.fvwm.org/screenshots/windowdecors/
>
> I have. It doesn't answer my question.

Well, configs of some samples do answer your question. AFAIR.

> In the meantime, I've been playing around and have learned a few things.
> It seemed at first as though I could have no more than 16 points, but
> this appears not to be the case, as I've now successfully created a
> vector button with 45 points.

The number of points was increased in 2.5.x two years ago. This is why
specifying fvwm version is always important.

> I have figured out the following:
>
> - A button without a function assigned to it will not be drawn, even
> if assigned a style.

I think this is in FAQ.

> - A button can only have a single vector chain. This isn't
> necessarily a problem, because vector segments can be made
> effectively invisible.

No, you may apply multiple AddButtonStyle as needed.

> - An error in the point list may cause the button not to be drawn, or
> may cause it to be drawn using a different ButtonStyle, depending
> on the nature of the error. The error may or may not be logged in
> .xsession-errors, and if logged, the message may or may not tell you
> anything useful about what the actual error was.

Well, you don't draw buttons very often to justify a complete syntax
error diagnostics system, do you? :)

> - I don't know if there's an upper limit to the number of points, but
> if so, it's at least 45.

It is 10000.

> - Although vector coordinates are on a scale of 1..100 (increments of
> 1%), the useful resolution is closer to increments of 5%, unless you
> have really friggin' HUGE buttons.

This is possibly because you use 3-d like relief that is 2 pixels wide.
If you use flat decorations, then entire 100% is available. I think.

> Anyway, after playing with this for a while, I've got two titlebar
> buttons and two sets of functions for sending windows to a specified
> page or a specified desk. The COMPLETE code, with vector buttons and
> window menu entries, follows. Note that I've now made the placement of
> the button panels smarter, as necessitated for titlebar button use; the
> old version of SendWindowToPage, if used on a titlebar button, would
> often appear partly offscreen. This version fixes that.
>
> Anyway, here's the code, and the attached PNG shows the appearance of
> the new buttons.

No time to read/play with this config for now. Maybe later.
Or you may just post a screenshot url.

Regards,
Mikhael.
--
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 Thu May 13 2004 - 21:05:51 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:56 BST