From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: circuitikz meters
Date: Tue, 1 Oct 2019 14:03:01 +1300 [thread overview]
Message-ID: <fb5a3ca8-901d-ae27-3f4b-17b1242178e4@gmail.com> (raw)
In-Reply-To: <2f4933cc82b5361d0a177f55c0eba74a9892db8e.camel@yahoo.com>
Circuitikz uses \textbf inside, which is a LaTeX macro. Unfortunately, this is
hardcoded within the ammeter and voltmeter nodes, so you can't easily change
it. Instead you can simply provide a macro that does the correct thing.
\usemodule[circuitikz]
\let\textbf\bold % <---
\starttext
\starttikzpicture
\draw (0,0)to[ammeter, t=A, i=$i$] ++(3,0);
\draw (0,4) to[rmeter, t=V, v>=$v$] ++(3,0) ;
\draw (0,2) to[voltmeter, l=$U$] (++3,2);
\stoptikzpicture
\stoptext
Cheers, Henri
On 10/1/19 5:07 AM, Martin Althoff wrote:
> Hello ...
>
> I am drawing some simple circuits for an electro-physics class I am teaching using
> circuitikz. Using meters gives some effects I don't quite understand.
>
> The MWE works as shown. The commented lines fail with "Undefined control sequence". If I
> put the same 3 lines into Latex (via Texstudio on Linux), just the opposite happens. The
> line with rmeter fails, the other two work.
>
> Why the difference? Some version issue? The "circuitikz manual version 0.9.4.pdf" shows
> all 3 types of meters as choice.
>
> Actually I would prefer to use the "ammeter" and "voltmeter" within Context.
>
> Thanks for any pointers.
>
> Greetings, Martin
>
> \usemodule[circuitikz]
> \starttext
> \starttikzpicture
> %\draw (0,0)to[ammeter, t=A, i=$i$] ++(3,0);
> \draw (0,4) to[rmeter, t=V, v>=$v$] ++(3,0) ;
> %\draw (0,2) to[voltmeter, l=$U$] (++3,2);
> \stoptikzpicture
> \stoptext
>
>
> Latex MWE, works as shown
>
> \documentclass{article}
> \usepackage{circuitikz}
> \begin{document}
> \begin{circuitikz}
> \draw (0,0) to[ammeter, t=A, i=$i$] ++(3,0);
> %\draw (0,4) to[rmeter, t=V, v>=$v$] ++(3,0) ;
> \draw (0,2) to[voltmeter, l=$U$] (++3,2);
> \end{circuitikz}
> \end{document}
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-10-01 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 16:07 Martin Althoff
2019-10-01 1:03 ` Henri Menke [this message]
2019-10-01 17:42 ` Martin Althoff
2019-10-01 18:10 ` Hans Hagen
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=fb5a3ca8-901d-ae27-3f4b-17b1242178e4@gmail.com \
--to=henrimenke@gmail.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).