ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <schultzk@uni-trier.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is this possible for the Frames
Date: Mon, 21 Oct 2013 09:38:46 +0200	[thread overview]
Message-ID: <CAC74FF5-F9D4-432B-B031-139293339BD6@uni-trier.de> (raw)
In-Reply-To: <8F7F697B-4791-4C69-BAB1-B9E3BCE81AE5@uni-trier.de>

Hi All,


Am 21.10.2013 um 08:41 schrieb "Keith J. Schultz" <schultzk@uni-trier.de>:

> Hi Wolfgang, all,
> 
> Thanx for the example/help.
> 
> I have a few questions sothat I understand properly what is going on and
> how to maybe do some more fancy things.
> 
> 1) \dimexpr allows the calculation of a dimention
> 
> 2)  \dimexpr is closed by \relax or if I need more complicated calculation something like:
> 	frameoffset=\dimexpr{\framedparameter{rulethickness}*3/10}  + \framedparameter{\frameoffset}}\relax
	Found the answer use \dimexpr(…). the \relax is so that TeX behaves!

> 3)  How would access a value of a DIFFERENT frame?
> 
> 4) I could use my own command whose result is a dimension:
>      \def\MyCommand#1{#1\textwidth}
> 	and use it as:
> 	frameoffset=\dimexpr\Mycommand{.05}\relax
> 
> regards
> 	Keith
> 

___________________________________________________________________________________
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:[~2013-10-21  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  9:25 Keith J. Schultz
2013-10-18 12:56 ` Wolfgang Schuster
2013-10-21  6:41   ` Keith J. Schultz
2013-10-21  7:38     ` Keith J. Schultz [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=CAC74FF5-F9D4-432B-B031-139293339BD6@uni-trier.de \
    --to=schultzk@uni-trier.de \
    --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).