From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: Images run into each other when using side floats
Date: Wed, 30 Oct 2019 17:16:21 +0100 [thread overview]
Message-ID: <20191030171621.13978607@homerow> (raw)
In-Reply-To: <nycvar.YAK.7.76.1910301154440.168402@ervasbepr.pvz.zptvyy.pn>
On Wed, 30 Oct 2019 11:55:17 -0400 (EDT)
Aditya Mahajan <adityam@umich.edu> wrote:
> On Wed, 30 Oct 2019, Marco Patzer wrote:
>
> > Hi!
> >
> > Some images run into each other when using floats. The following
> > example illustrates this. The second image (or frame) runs into the
> > side figure frame. How to prevent this?
> >
> > \setupfloat [figure] [default=left]
> >
> > \starttext
> > \samplefile{knuth}
> >
> > \startplacefigure [title=Foo]
> > \framed [width=5cm, height=5cm]{}
> > \stopplacefigure
> >
> > \samplefile{ward} \blank
> Add:
>
> \dontleavehmode
Thanks for the nudge in the right direction.
Is there a way to include the \dontleavehmode in the combinations?
The frame is actually a combination (removed while creating MWE).
The before key from \setupcombinations doesn't seem to do the right
thing here. If that's possible I can leave the sources as they are.
\setupfloat [figure] [default=left]
\starttext
\samplefile{knuth}
\startplacefigure [title=Foo]
\framed [width=5cm, height=5cm]{}
\stopplacefigure
\samplefile{ward} \blank
\dontleavehmode
\startcombination [1*1]
\startcontent \framed [width=4cm, height=4cm]{} \stopcontent
\startcaption Foo \stopcaption
\stopcombination
\samplefile{knuth}
\stoptext
Marco
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-10-30 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 15:41 Marco Patzer
2019-10-30 15:55 ` Aditya Mahajan
2019-10-30 15:57 ` Wolfgang Schuster
2019-10-30 16:16 ` Marco Patzer [this message]
2019-10-30 17:48 ` Wolfgang Schuster
2019-10-30 18:40 ` Marco Patzer
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=20191030171621.13978607@homerow \
--to=lists@homerow.info \
--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).