ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <context@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: FLOW chart module broken
Date: Mon, 28 Nov 2011 13:07:06 +0100	[thread overview]
Message-ID: <D63E976E-5ED6-439E-A099-47ADB35FBDBB@boede.nl> (raw)
In-Reply-To: <4ED37513.7080400@wxs.nl>

Hans,

there is in the original version of this module a command \setupfFLOWsplit which precisely is meant for this. When calling the flow chart with \FLOWcharts[Eenkaternbinding] instead of \FLOWchart[Eenkaternbinding] it splitted over pages.

\setupFLOWsplit
    [x=1,
    y=1,
    nx=6,
    ny=7,
    dx=1,
    dy=1,
    before=,
    after=\page,
    marking=off]

Willi
On 28 Nov 2011, at 12:48, Hans Hagen wrote:

> On 28-11-2011 11:50, Willi Egger wrote:
>> Hi Otared,
>> 
>> thanks for your testing!
>> 
>> hm, yes without \starttext and stoptext ... (this file is loaded in a larger context with \input), so I missed this, BAD!
>> 
>> Still this is very strange. I use the same version of Context as you did. Still I do not get the flowchart breaking over pages. I can restrict the number of cells in the \setupflowcharts command and get then accordingly a shorter piece of the chart but no following pages (the chart is about 2 pages long).
>> When setting the nx to some large number the flowchart is compiled, but there is only a single page of cells which is typeset beyond the lower margin.
> 
> What makes you expect that a chart breaks over pages?
> 
> Hans
> 
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                             | 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
___________________________________________________________________________________


      reply	other threads:[~2011-11-28 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 15:15 Willi Egger
2011-11-27 20:27 ` Otared Kavian
2011-11-28 10:50   ` Willi Egger
2011-11-28 11:48     ` Hans Hagen
2011-11-28 12:07       ` Willi Egger [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=D63E976E-5ED6-439E-A099-47ADB35FBDBB@boede.nl \
    --to=context@boede.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).