Hi everyone, I have tested the minimal example mentioned above on a completely separate Linux installation, and I am seeing the same observable artifact. This leads me to believe that the issue might not be specific to my context installation. It seems that the overlay in the heading and the \shape{product} are essential components that trigger the behavior I’m experiencing. At this point, I'm uncertain whether this is an error on my part or a potential bug—possibly related to flowcharts. Could someone please confirm if the output of the minimal example matches what is shown in the attached PDF? Thank you! Best, Bernd Am Fr., 11. Okt. 2024 um 22:47 Uhr schrieb Bernd Donner < bleau1975@googlemail.com>:
Hi,
I have a broken flow cell connection in this minimal example. The broken flow cell is only triggered when drawn within a subsection with an overlay. The logic to create the underlined subsection is by the way copied from the metafun manual source. I do not have the slightest clue what is going wrong in this example. Thanks for ideas.
Best, Bernd
\usemodule[chart]
\startuniqueMPgraphic{SectionUnderline} path p; p:= unitsquare xscaled OverlayWidth yscaled OverlayHeight; draw llcorner p -- lrcorner p; setbounds currentpicture to p; \stopuniqueMPgraphic
\defineoverlay[SectionUnderline][\uniqueMPgraphic{SectionUnderline}]
\starttexdefinition unexpanded ChapterCommand #1#2 \framed [background=SectionUnderline] {#2} \stoptexdefinition
\setuphead [subsection] [command=\ChapterCommand]
\starttext
\subsection[title=Introduction]
\startFLOWchart[toolchain]
\startFLOWcell \location{1,1} \connection [bt] {compiler} \stopFLOWcell
\startFLOWcell \name {compiler} \location{1,2} \shape{product} \stopFLOWcell \stopFLOWchart
\FLOWchart[toolchain] \stoptext