From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Gavin <gavinpublic@comcast.net>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Mathematical MetaFun Mania
Date: Thu, 15 Dec 2022 18:21:52 +0100 [thread overview]
Message-ID: <b1a9ab27-83b0-139d-9f6b-f51039c00e8e@freedom.nl> (raw)
In-Reply-To: <4D785BE1-91F2-4E90-82A9-155E7E29DBC9@comcast.net>
On 12/15/2022 5:15 PM, Gavin wrote:
> Hi Hans and List,
>
>>> 2) Can I tell \connectboxanchors to use my MetaPost code and pass key=value pairs like I do with \setMPpositiongraphic?
>> see attached ... the 'cross pages' feature is in the upcoming
>
> This indeed passes key=value pairs, but I cannot get it to pass mine. Is there some intermediate step? Your example has a key=value pair in \connectboxanchors and which is accessed in the MetaPost code. The pair, and MetaPost code are:
>
> rulethickness=1pt
> mpvard “rulethickness"
>
> However, if I change the pair and MPcode to (see attached example for full code)
>
> myrulethickness=1pt
> mpvard “myrulethickness"
>
> it doesn’t work. Similarly, you have a pair and MPcode that don’t match.
>
> rulecolor=darkgreen
> mpvars "linecolor"
>
> This may be a historical fluke, but it suggests that there is some intermediate translation that I am missing. Any way I can name and pass by own key=value pairs?
I updated lmtx so you can test it again.
Hans
ps. For the adventurous some bonus experiment in the engine:
\def\ccc#1#2#3#4#5#6#7#8#9#A#B#C#D#E#F%
{\def\ddd{#A-#D-#E/#F-#4-#1}%
#A-#D-#E/#F-#4-#1+\ddd}
so, upto 15 arguments:
[[\ccc123456789abcdef]]
(not that we need it in the context core, so more a gimmick for users
and it fits the much is already hex approach)
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://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-15 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 3:20 Gavin via ntg-context
2022-12-15 10:36 ` Hans Hagen via ntg-context
2022-12-15 16:15 ` Gavin via ntg-context
2022-12-15 17:21 ` Hans Hagen via ntg-context [this message]
2022-12-15 21:54 ` Otared Kavian via ntg-context
2022-12-16 16:42 ` Hans Hagen via ntg-context
2022-12-16 16:55 ` Hans Hagen via ntg-context
2022-12-18 11:03 ` Alexandre Christe via ntg-context
2022-12-21 14:05 ` Gavin via ntg-context
2022-12-21 14:29 ` Sans Math fonts, for example Computer Modern Bright Oliver Sieber via ntg-context
2022-12-21 14:41 ` Mikael Sundqvist via ntg-context
2022-12-21 16:00 ` Mathematical MetaFun Mania Hans Hagen 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=b1a9ab27-83b0-139d-9f6b-f51039c00e8e@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=gavinpublic@comcast.net \
--cc=j.hagen@freedom.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).