ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: listoffloats question
Date: Fri, 1 Sep 2006 13:07:13 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.63.0609011259550.12262@rrpf4327h10.ratva.hzvpu.rqh> (raw)
In-Reply-To: <opte7j72k79niby6@localhost>



On Fri, 1 Sep 2006, nico wrote:

> On Fri, 01 Sep 2006 17:14:01 +0200, richard rascher-friesenhausen
> <richard@mevis.de> wrote:
>
>> Hello,
>>
>> in my scripts i use different kinds of figure, defined as floats cloned
>> from the original ConTeXt figure:
>>
>> \definefloat[afigure][afigures][figure]
>> \definefloat[bfigure][bfigures][figure]
>>
>> In my script environment i use different setups for figure, afigure and
>> bfigure that are not shown here.
>> Using cloning, all figures use the same counter, which is nice.
>
> Really? In which release the counter is the same? With your case, I have
> here the figure numbers 1, 1, 1, 2, 2, 2.

I confirm that with the latest beta, I get the same results. But looking 
at the definition of redodefinefloat this should work.

\def\redodefinefloat[#1][#2][#3]% same label/number
%[snip]
    \definenumber[#1][#3]%
%[snip]

This means that the number #1 and #3 should be coupled. A simple test 
confirms this

\definenumber[one]
\definenumber[two][one]


\starttext

one: \getnumber[one]
\incrementnumber[two]

one: \getnumber[one]

two: \getnumber[two]

\stoptext

I do not understand why this should fail with definefloat.

BTW, why is the definition of redodefinefloat repeated in the source?

Aditya

  reply	other threads:[~2006-09-01 17:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 15:14 richard rascher-friesenhausen
2006-09-01 16:32 ` nico
2006-09-01 17:07   ` Aditya Mahajan [this message]
2006-09-01 19:37   ` Hans Hagen
2006-09-04 12:12   ` richard rascher-friesenhausen
2006-09-04 18:05     ` Willi Egger
2006-09-05  8:05       ` richard rascher-friesenhausen
2006-09-05  9:52         ` Willi Egger
2006-09-06 21:32         ` Hans Hagen
2006-09-07  7:44           ` richard rascher-friesenhausen
2006-09-07 16:24             ` 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=Pine.GSO.4.63.0609011259550.12262@rrpf4327h10.ratva.hzvpu.rqh \
    --to=adityam@umich.edu \
    --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).