From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Artifact in flow cell connection
Date: Wed, 16 Oct 2024 20:47:36 +0200 [thread overview]
Message-ID: <94c46203-e595-4310-9ca2-1907a44f1c8a@xs4all.nl> (raw)
In-Reply-To: <64D32432-DDCA-4B79-882E-795105BC2532@scorecrow.com>
On 10/16/2024 7:48 PM, Bruce Horrocks wrote:
>
>
>> 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}}]
You don't want that framed command in the table of content entry, so use
\setuphead
[subsection]
[textcommand={\inframed[frame=off,bottomframe=on]}]
or
\definebar[SubSectionBar][underbar][offset=-1]
\setuphead[subsection][textcommand=\SubSectionBar]
instead,
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 / 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 18:53 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
2024-10-16 18:47 ` Hans Hagen [this message]
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=94c46203-e595-4310-9ca2-1907a44f1c8a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).