ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "autumnus " <ai2472206007@yeah.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] issue when the encapsulation ‘startitem stopitem’ command is in another self-defined command
Date: Sat, 28 Dec 2024 12:34:35 -0000	[thread overview]
Message-ID: <173538927531.1763.1030629409830318898@cgl.ntg.nl> (raw)

hi,

I'm creating a command that can format multiple choice questions on my own. 
I've done most of it at the moment. 
But I want more, so I'm trying to create more versions of this command 
that is already nearing completion. 
So I'm using the following command to create a command with more possibilities.

I've noticed that ‘startitem stopitem’ isn't working. 
Their location and serial number are anomalous.

%%%% Removed some unnecessary commands to show what the problem was.
% macros=mkvi
\starttext
\unprotect
\installnamespace          {chitem}
\installcommandhandler \????chitem     {chitem}     \????chitem

\appendtoks
 \setuevalue{\e!start\currentchitem}{\startnamedchitem [\currentchitem]}%
 \setuevalue{\e!stop \currentchitem}{\stopnamedchitem}%
\to \everydefinechitem

\tolerant\protected\def\markedchoice#1{{\sym{@} \red sym : #1}}
\tolerant\protected\def\normalchoice#1{\startitem normal : #1\stopitem}
\tolerant\protected\def\\calc_maxwidth#1{}
%The longest option text is calculated by comparison to
%  determine the number of columns that can be typeset

\tolerant\protected\def\startnamedchitem[#chitem]#*[#mark]#*[#option]#*#choice\stopnamedchitem%
 {\begingroup
%  \ifarguments 0\or :1\or +2\or =3\or !4\fi
  \def\currentchitem{#chitem}%
  \edef\p_correctmark{*}\edef\p_paramark{#mark}%
  \calc_maxwidth{#choice}%
  \ifx\p_paramark\p_correctmark
      \markedchoice{#choice}%
  \else
      \normalchoice{#choice}%
  \fi\endgroup}
  
\def\stopnamedchitem{}
\definechitem[chitem]
\protect

\startitemize[n,horizontal,two]% 
% The process of calculating the number of formattable columns 
% has been removed and the results of the calculations are used directly.
\startchitem xxx\stopchitem
\startchitem[*]correct choice\stopchitem
\startchitem xxx\stopchitem
\startchitem xxx\stopchitem
\stopitemize

\stoptext
%%%%%

thanks for any help,
autumnus
___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2024-12-28 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28 12:34 autumnus  [this message]
2024-12-28 13:22 ` [NTG-context] " Wolfgang Schuster
2024-12-28 14:14   ` autumnus 
2024-12-28 14:44   ` autumnus 
2024-12-29 18:37     ` Wolfgang Schuster

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=173538927531.1763.1030629409830318898@cgl.ntg.nl \
    --to=ai2472206007@yeah.net \
    --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).