From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Square pens and dash pattern
Date: Wed, 6 Apr 2016 10:01:31 +0200 [thread overview]
Message-ID: <CAG5iGsBxY=pCTV+AVKo7fOiJ2xziaAWnQX2Xng17nqCEYJD5gg@mail.gmail.com> (raw)
In-Reply-To: <5704C05A.7030401@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1940 bytes --]
On Wed, Apr 6, 2016 at 9:52 AM, Hans Hagen <pragma@wxs.nl> wrote:
> On 4/6/2016 1:44 AM, Aditya Mahajan wrote:
>
>> Hi,
>>
>> There appears to be a metapost bug with square pens and dash patterns:
>>
>> \starttext
>>
>> \startMPcode
>> pickup pencircle scaled 1bp;
>> drawarrow origin -- (5cm, 4cm) dashed evenly;
>> pickup pensquare scaled 1bp;
>> drawarrow origin -- (5cm,-4cm) dashed evenly;
>> \stopMPcode
>>
>> \stoptext
>>
>> Note that the second arrow is not dashed at all! This is not due to the
>> thick pen.
>>
>
> pencircles make simple round pens that are mapped directly onto ps
> primitives and there dashing applies (dashing is just passing data to the
> backend) ... afaik other penshapes can result in a filled path so no
> dashing applies
>
> (but mp master luigi will tripple check it in the source for you so he
> might come up with another answer)
>
> (and after that, as mathematical challenge, alan will write a mp macro
> that fakes the dashing)
>
> Hans
>
>
# cat test-square.mp test-circle.mp
beginfig(1);
tracingall;
%pickup pencircle scaled 1bp;
%drawarrow origin -- (5cm, 4cm) dashed evenly;
pickup pensquare scaled 1bp;
drawarrow origin -- (5cm,-4cm) dashed evenly;
endfig;
end.
beginfig(1);
tracingall;
pickup pencircle scaled 1bp;
drawarrow origin -- (5cm, 4cm) dashed evenly;
%pickup pensquare scaled 1bp;
%drawarrow origin -- (5cm,-4cm) dashed evenly;
endfig;
end.
# mpost test-square.mp
says, near the end,
Edge structure at line 7 (just shipped out):
Filled pen stroke :
(0,0)..controls (47.24408,-37.79527) and (94.48817,-75.59053)
..(141.73225,-113.3858)
dashed (on 3 off 3) shifted 0 (this will be ignored)
while
# mpost test-circle.mp
says
Edge structure at line 7 (just shipped out):
Filled pen stroke :
(0,0)..controls (47.24408,37.79527) and (94.48817,75.59053)
..(141.73225,113.3858)
dashed (on 3 off 3) shifted 0
So it doesn't look a mpost bug .
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 3490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-04-06 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 23:44 Aditya Mahajan
2016-04-06 0:59 ` Alan BRASLAU
2016-04-06 7:52 ` Hans Hagen
2016-04-06 8:01 ` luigi scarso [this message]
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='CAG5iGsBxY=pCTV+AVKo7fOiJ2xziaAWnQX2Xng17nqCEYJD5gg@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/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).