ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re[3]: sidebyside figures
Date: Tue, 11 Mar 2003 15:44:56 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20030311153653.02626120@server-1> (raw)
In-Reply-To: <5611436845.20030311132603@iol.it>

At 01:26 PM 3/11/2003 +0100, you wrote:

>Yup, floatcaptions can do it all, nice. Now the question is: is it
>normal for the combination to stick to the left margin? Shouldn't

hm, it probably is when you put some \maxdimen width content in it

>it be centered horizontally? I can achieve the effect by
>surrounding it with \midaligned{...} (i.e.
>\midalgined{\startcombination ... \stopcombination}) but it would
>be nice if it could be set as an option to combinations ...

Hey, since when don't you read source code any more?

\starttext

\showframe

\definieerplaats[mine][location=middle] % have to cook up a 
[english..italian] name for that one

\setupcombinations[align=left,location=top]

\placemine \bgroup \startcombination
   {\externalfigure[cow][width=3cm,height=2cm]} {cow}
   {\externalfigure[cow][width=3cm,height=1cm]} {cow}
\stopcombination \egroup

\stoptext

(this placement command also takes care of spacing, grid snapping and so, 
but should only be used in the mlv, not for instance inside floats; it's 
the same placement that is used in \startframedtext; you can define 
combinations btw)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2003-03-11 14:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09  1:08 Problem with references Stefan Karlsson
2003-03-09  2:35 ` sidebyside figures Lei Wang
2003-03-09  9:03   ` Guy Worthington
2003-03-09 17:25     ` Lei Wang
2003-03-09 21:29   ` Hans Hagen
2003-03-10  4:47     ` Lei Wang
2003-03-10 22:15       ` Hans Hagen
2003-03-11  9:27         ` Re[2]: " Giuseppe Bilotta
2003-03-11 10:49           ` Hans Hagen
2003-03-11 12:26             ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:44               ` Hans Hagen [this message]
2003-03-11 17:01                 ` Re[4]: " Giuseppe Bilotta
2003-03-12 10:21                   ` Hans Hagen
2003-03-12 14:00                     ` Re[5]: " Giuseppe Bilotta
2003-03-12 15:03                       ` Hans Hagen
2003-03-13  9:28                         ` Re[6]: " Giuseppe Bilotta
2003-03-11 17:47           ` Re[2]: " K.H. Wesseling
2003-03-12 14:01             ` Re[4]: " Giuseppe Bilotta
2003-03-11 20:48         ` Lei Wang
2003-03-12  0:48           ` K.H. Wesseling
2003-03-10  4:48     ` Lei Wang
2003-03-09  2:42 ` Problem with references Guy Worthington
2003-03-09  9:51   ` Stefan Karlsson
2003-03-09 12:04   ` Stefan Karlsson

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=5.1.0.14.1.20030311153653.02626120@server-1 \
    --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).