From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: MetaFun refill/do_repath bug
Date: Mon, 16 Sep 2002 22:03:27 +0200 [thread overview]
Message-ID: <20020916220327.3539dac6.morawski@gmx.net> (raw)
In-Reply-To: <5.1.0.14.1.20020916181949.01fe9808@server-1>
On Mon, 16 Sep 2002 18:29:55 +0200
Hans Hagen <pragma@wxs.nl> wrote:
> At 05:31 PM 9/16/2002 +0200, Jens-Uwe Morawski wrote:
> >Your macro ignores totally that clipped and bounded elements
> >contain again some more graphic elements, i.e. lines, filled
> >paths etc. Therefore the macro has to be applied recursively to
> >these elements too. Furthermore the pathpart of a clipped
> >or bounded object has to be applied only to the elements in
> >that object and not to the whole picture.
>
> hm, will look into it, kind of funny that "i" then is a path and picture at
> the same time
the i in the loop is always a picture but the macro pathpath extracts
the path information. for clipped and bounded objects these paths are
the clip or setbounds paths.
> >Please find below a MP-file that illustrates what i mean.
> >It compares the macro "uniformfilled" from my article with
> >your "refill".
>
> btw, a real robust solution also takes fonts into account so i'll have a
> look at that (fontpart and textpart)
you need more since fontpart and textpart do not include the
transformations applied to the text. But, since i in a
for i within a_picture
is always a picture, text elements can be handled easily with
addto ... also i ; The test for textual and textpart/fontpart
is only needed if you really want to work with the text-information.
In order to rewrite all text in blue it should be enough to say:
if textual i:
addto tmp_pic also i withcolor blue ;
fi;
Jens
next prev parent reply other threads:[~2002-09-16 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:31 Jens-Uwe Morawski
2002-09-16 16:29 ` Hans Hagen
2002-09-16 20:03 ` Jens-Uwe Morawski [this message]
2002-09-17 7:57 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020916220327.3539dac6.morawski@gmx.net \
--to=morawski@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).