ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Bug in lmt_arrow
Date: Sun, 14 Nov 2021 14:02:18 +0100	[thread overview]
Message-ID: <caedf581-b090-2397-5a86-7fc181513052@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2111132229210.949070@nqv-guvaxcnq>

On 11/14/2021 4:33 AM, Aditya Mahajan via ntg-context wrote:
> Hi,
> 
> There is a bug in lmt_arrow. If given a "non-cycle" path, lmt_arrow completes the cycle.
> 
>      \starttext
> 
>      \startMPcode
>        newpath p;
>        ahfactor := 5;
>        p := origin .. (1cm, 1cm) .. (2cm, 0);
>        draw lmt_arrow
>             [
>               path = p,
>               location = "percentage",
>               percentage = 50,
>               alternative = "curved",
>             ]
>             withpen pencircle scaled 1bp;
>      \stopMPcode
>      \stoptext
> 
> With 2021.11.11, I get the attached file. Note that lmt_arrow has drawn the "cycle" version of the path, even though p does not have a cycle.
> 
> I have looked at the code and cannot figure out why this is happening.

it happens in the 'direct' variant (metapost.registerdirect) where a 
boolean is passed as signal and that boolean then is also picked up by 
the (shared) path injector as (old school) signal that a path is closed 
while it should instead consutl the closed field in a path table (sounds 
more complex than it is)

so in the end it is a nasty side effect of the fast inject code path 
(shared function with different stack values; i'll probably have to 
ditch a "low level backward compatibility feature no one uses anyway" 
some day)

i uploaded a fix that you can test when the bins are compiled at

	https://build.contextgarden.net/#/waterfall?tags=c.luametatex

new bins then in:

	https://dl.contextgarden.net/build/luametatex/

(fyi: in the mp code you see that the path p is 'get' from the lua end 
where it got passed to by parameter)

(interesting that it didn't show up sooner, maybe most users have closed 
paths and/or most lmt_ features used closed paths)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-11-14 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  3:33 Aditya Mahajan via ntg-context
2021-11-14 13:02 ` Hans Hagen via ntg-context [this message]
2021-11-15  2:49   ` Aditya Mahajan via ntg-context
2021-11-15  3:07     ` Aditya Mahajan via ntg-context
2021-11-15 10:05       ` Hans Hagen via ntg-context
2021-11-20  5:53         ` Aditya Mahajan via ntg-context
2021-11-20 11:41           ` Hans Hagen via ntg-context
2021-11-22  3:21             ` Aditya Mahajan via ntg-context

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=caedf581-b090-2397-5a86-7fc181513052@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).