ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Size of the last shipped page by Lua?
Date: Fri, 23 Sep 2016 15:00:39 +0200	[thread overview]
Message-ID: <91e2727f-e58c-2067-9282-8bbb3fb2c668@wxs.nl> (raw)
In-Reply-To: <op.yn8q5rny62epfj@lpr>

On 9/23/2016 1:50 PM, Procházka Lukáš Ing. wrote:
> Hello,
>
> still a problem - consider the following code:
>
> ----
> \ifx\startpapersize\undefined
>   \unprotect
>     \def\startpapersize{\page\pushmacro\page_paper_restore\setuppapersize}
>   \protect
> \fi
>
> \ifx\stoppapersize\undefined
>   \unprotect
>     \def\stoppapersize{\page\popmacro\page_paper_restore\setuppapersize}
>   \protect
> \fi
>
> %
>
> \startluacode
>   local tomm = function(v) return v * (210 / 39158276) end
>
>   pgsz = function()
>     context("w=%.1f, h=%.1f", tomm(tex.dimen.paperwidth),
> tomm(tex.dimen.paperheight))
>   end
> \stopluacode
>
> %
>
> \starttext
>   A
>   \ctxlua{pgsz()}
>
>   \startpapersize[A3,landscape]
>     B
>     \ctxlua{pgsz()}
>   \stoppapersize
>
>   \startTEXpage[width=200mm,height=100mm]
>     C % 3rd page
>     \ctxlua{pgsz()}
>   \stopTEXpage

the papersize of a TEXpage is known when that page is flushed and when 
you ask for it the way you do now tex is still constructing the box

it's all a matter of timing

\starttext

\appendtoks
     \ctxlua{
         print(
             number.topoints(tex.dimen.paperwidth ),
             number.topoints(tex.dimen.paperheight)
         )
     }%
\to \everyshipout

\setuppapersize[A4] test

\startTEXpage test \stopTEXpage

\setuppapersize[A3] test

\stoptext


> \stoptext
> ----
>
> In the case of 3rd page (with text "C"), page size "w=210.0, h=297.0" is
> printed instead of "w=200.0, h=100.0".
>
> So how to access values 200 and 100 mm for the page produced by
> \startTEXpage[width=...,height=...]?
>
> Best regards,
>
> Lukas
>
>
> On Thu, 08 Sep 2016 22:12:49 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 9/8/2016 9:47 PM, josephcanedo@gmail.com wrote:
>>> If by messing it’s meant modifying their values, I agree that’s a bad
>>> idea 😊, the requirement is likely to read the value only (at least this
>>> is my usage of these in shipouts « after » callback).
>>>
>>> If these are not reliable, what’s the reliable way to get the page width
>>> and height ?
>>
>> \starttext
>>
>> \ctxlua{context(number.topoints(tex.dimen.paperwidth))}
>>
>> \ctxlua{context(number.topoints(tex.dimen.paperheight))}
>>
>> \stoptext
>>
>>
>> -----------------------------------------------------------------
>>                                            Hans Hagen | PRAGMA ADE
>>                Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>>         tel: 038 477 53 69 | www.pragma-ade.nl | 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
>> ___________________________________________________________________________________
>>
>
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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:[~2016-09-23 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:12 Procházka Lukáš Ing.
2016-09-07 19:39 ` josephcanedo
2016-09-07 22:21   ` Hans Hagen
2016-09-08 19:47     ` josephcanedo
2016-09-08 20:12       ` Hans Hagen
2016-09-12  6:13         ` Procházka Lukáš Ing.
2016-09-23 11:50         ` Procházka Lukáš Ing.
2016-09-23 13:00           ` 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=91e2727f-e58c-2067-9282-8bbb3fb2c668@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).