Changes

Jump to navigation Jump to search
863 bytes added ,  13:39, 22 February 2016
a workaround of the "reset counter" bug; the names of the counters' commands
\setnumber[mynumber][42]
\doifelse{\getnumber[mynumber]}{42}{
Strange, \type{\tt getnumber} worked.
}{
Using \type{\tt getnumber} does not work.
}
\doifelse{\rawcountervalue[mynumber]}{42}{
Ok, the test with \type{\tt rawcountervalue} worked.
}{
Strange, \type{\tt rawcountervalue} failed.
}
</texcode>
 
== Forcing the Reset of a Counter ==
Due to a current bug[http://www.mail-archive.com/ntg-context%40ntg.nl/msg78847.html], counters are reset by chapter, page, etc. only when they are incremented.
To force the reset, you can increment and then decrement a counter before using it.
<texcode>
\definecounter[mycounter][way=bypage]
\setcounter[mycounter][10]
\rawcountervalue[mycounter]
\page % new page, mycounter should be reset
\rawcountervalue[mycounter] % no, it's not reset: you still get '10'
 
\incrementcounter[mycounter]\decrementcounter[mycounter]
\rawcountervalue[mycounter] % now you should get '0' because it has been reset
</texcode>
 
== \definenumber or \definecounter ? ==
In ConTeXt MkIV {{cmd:definecounter}}, {{cmd:incrementcounter}}, etc. seem to be preferred to {{cmd:definenumber}}, {{cmd:incrementnumber}}, etc.
== Names of Commonly Used Counters ==
26

edits

Navigation menu