ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: currentreferencerealpage wrong (how to detect even/odd pages?)
Date: Mon, 16 Mar 2015 11:27:41 +0100	[thread overview]
Message-ID: <5506B01D.5010107@wxs.nl> (raw)
In-Reply-To: <20150315191351.GA26046@hl.fritz.box>

On 3/15/2015 8:13 PM, Harald Koenig wrote:
> On Mar 15, Wolfgang Schuster wrote:
>
>>
>>> Am 15.03.2015 um 16:40 schrieb Harald Koenig <koenig@tat.physik.uni-tuebingen.de>:
>>>
>>> Hi,
>>>
>>> right now I use \currentreferencerealpage to detect if I'm on an even or odd page
>>> (because my picture placement rules depend on it) like this:
>>>
>>> \newcount\bildpage
>>> \bildpage=1
>>> % ...
>>> \def\bild#1...{%
>>>      {\global\bildpage=\realpageno}%
>>>      \ifodd\bildpage \def\eo{o}\else \def\eo{e}\fi
>>>      % ...
>>>      \if o\eo odd...\else even...\fi
>>>     \message{>> bildpage=\the\bildpage \space eo=\eo \space currentreferencerealpage=\currentreferencerealpage \space << }%
>>> }
>>>
>>> but now I notice that for some pages/pictures the value of \currentreferencerealpage
>>> is not correct (only for the first picture on a new page?):-(
>>
>> To test whether you’re on a left or right page you can use the \signalrightpage and \doifrightpageelse commands
>
> this doesn't seem to work well -- at least not within \placefigure
>
> I've tried this replacement in my \bild macro which should be equivalent (or better?)
>
> %   \ifodd\bildpage \def\eo{o}\else \def\eo{e}\fi
> %   \ifodd\bildpage \def\lr{r}\else \def\lr{l}\fi
>      \dontleavehmode\signalrightpage
>      \doifrightpageelse{\def\eo{o}}{\def\eo{e}}%
>      \doifrightpageelse{\def\lr{r}}{\def\lr{r}}%
>
> (with and without \dontleavehmode\signalrightpage)
> and now I get more wrong picture placements for the first picture on some pages...

you need to make sure that the signal travels with the stuff you're 
checking

btw, if you use side floats, the inner/outer variants do this auto 
left/right stuff

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2015-03-16 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 15:40 Harald Koenig
2015-03-15 15:43 ` Harald Koenig
2015-03-15 16:51 ` Wolfgang Schuster
2015-03-15 19:13   ` Harald Koenig
2015-03-16 10:27     ` Hans Hagen [this message]

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=5506B01D.5010107@wxs.nl \
    --to=pragma@wxs.nl \
    --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).