From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>, a badin <andrej.badin@gmail.com>
Subject: Re: \externafigure and \at do not work together
Date: Sun, 31 Oct 2021 13:03:28 +0000 [thread overview]
Message-ID: <10A13523-F532-4494-B035-98271540F315@scorecrow.com> (raw)
In-Reply-To: <CAKiWGL4heuziTG5P0+UOU4H5T1VDexq2nek2tMWoHAKvw9DDUA@mail.gmail.com>
I thought it was necessary to use one of the derivations of \placefloat in order to get the reference generated. In your case this would be \placefigure thus:
\starttext
\placefigure [ ] [clock] { } {\externalfigure[clock.jpg]}
\at[clock] refers to a clock
\stoptext
> On 31 Oct 2021, at 12:49, a badin via ntg-context <ntg-context@ntg.nl> wrote:
>
> The fix is not really a fix thought, as it makes the image of the
> figure disappear.
> Still don't know how to make a .jpg work with \at
>
> On Sun, 31 Oct 2021 at 13:07, a badin <andrej.badin@gmail.com> wrote:
>>
>> Hello, perhaps this is how it is supposed to work, but:
>>
>> \externalfigure[clock.jpg][clock]
>> \starttext
>> \at[clock] refers to a clock
>> \stoptext
>>
>> produces "?? refers to a clock", instead of "1 refers a clock" --- the
>> wiki of \at says, that labels of figures can be refered to. Is this a
>> bug, or can only some labels be refered to? I was able to fix it
>> using:
>>
>> \reference[clock]{\externalfigure[clock.jpg]}
>> \starttext
>> \at[clock] refers to a clock
>> \stoptext
>>
>> and
>>
>> \externalfigure[clock][]
>> \starttext
>> \at
>> \stoptext
>>
>> produces an interesting artwork... so I thought maybe this could be a
>> bug. LMTX 2021.10.21
>>
>> Best,
>> Andrej
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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:[~2021-10-31 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 12:07 a badin via ntg-context
2021-10-31 12:49 ` a badin via ntg-context
2021-10-31 13:03 ` Bruce Horrocks via ntg-context [this message]
2021-10-31 17:11 ` Otared Kavian via ntg-context
2021-11-01 11:40 ` Wolfgang Schuster 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=10A13523-F532-4494-B035-98271540F315@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=andrej.badin@gmail.com \
--cc=ntg@scorecrow.com \
/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).