ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>, Taco Hoekwater <taco@elvenkind.com>
Subject: Re: floats disturb section placement (solved)
Date: Sun, 15 May 2011 15:36:22 +0200	[thread overview]
Message-ID: <D0A6A42F-E7E1-4807-BBAB-32C693794402@st.estfiles.de> (raw)
In-Reply-To: <37111ECA-001C-4893-9629-07E698B81130@st.estfiles.de>



> Von: Hans Hagen <pragma@wxs.nl>
> Datum: 15. Mai 2011 14:09:27 MESZ
> Betreff: Re: [NTG-context] (URGENT) floating objects causing bug
...

> in spac-ver.lua this helps ...
> 
> --~                                 ps = writable_spec(previous) -- no writable needed here
> --~                                 ps.width, ps.stretch, ps.shrink = pw + cw, pp + cp, pm + cm
> previous.spec = nodes.pool.gluespec(pw + cw, pp + cp, pm + cm)
> 
> so, we run into this writable mess again (maybe copying a gluespec in the engine when a topskip is injected is the best solution) ... ok, eventually gluespecs will become fields in a glue node so it's a temporary roblem


... and it helps solving the problem described in this thread, too!!


Great. Thank you Hans!

Steffen
___________________________________________________________________________________
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:[~2011-05-15 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 10:29 floats disturb section placement Steffen Wolfrum
2011-05-15 13:36 ` Steffen Wolfrum [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=D0A6A42F-E7E1-4807-BBAB-32C693794402@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=taco@elvenkind.com \
    /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).