From: Bruce Horrocks <ntg@scorecrow.com>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bernd Donner <bleau1975@googlemail.com>
Subject: [NTG-context] Re: Artifact in flow cell connection
Date: Wed, 16 Oct 2024 18:48:17 +0100 [thread overview]
Message-ID: <64D32432-DDCA-4B79-882E-795105BC2532@scorecrow.com> (raw)
In-Reply-To: <CAO4UkVbBDN0g=EkkKoC=MXANDBctT==pJWmzPV-t-wexBqKSOg@mail.gmail.com>
> On 15 Oct 2024, at 07:47, Bernd Donner via ntg-context <ntg-context@ntg.nl> wrote:
>
> Could someone please confirm if the output of the minimal example matches what is shown in the attached PDF?
I too get the output as posted. (mtx-context | current version: 2024.09.25 11:53)
If you change the following MWE line
\connection [bt] {compiler}
to
\connection [br] {compiler}
then the glitch goes away, so I suggest that means it is a bug in the flow chart module.
Changing to draw from the bottom shape upwards also has the glitch on a straight line - so something to do with the straight line drawing code, perhaps?
As a work-around, if you just want the section heading underlined (as opposed to a more complicated MP graphic that you omitted for simplicity) then your MWE becomes:
\usemodule[chart]
\starttext
\subsection[title={\inframed[frame=off,bottomframe=on]{Introduction}}]
\startFLOWchart[toolchain]
\startFLOWcell
\location{1,1}
\connection [bt] {compiler}
\stopFLOWcell
\startFLOWcell
\name {compiler}
\location{1,2}
\shape{product}
\stopFLOWcell
\stopFLOWchart
\FLOWchart[toolchain]
\stoptext
If you don’t want the section number then use \subsubject instead of \subsection.
Regards,
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-10-16 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 20:47 [NTG-context] " Bernd Donner via ntg-context
2024-10-15 6:47 ` [NTG-context] " Bernd Donner via ntg-context
2024-10-16 17:48 ` Bruce Horrocks [this message]
2024-10-16 18:47 ` Hans Hagen
2024-10-16 20:28 ` Hans Hagen via ntg-context
2024-10-17 14:39 ` Bernd Donner via ntg-context
2024-10-12 7:03 wangzhongtian
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=64D32432-DDCA-4B79-882E-795105BC2532@scorecrow.com \
--to=ntg@scorecrow.com \
--cc=bleau1975@googlemail.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).