From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Superimposing two flowcharts
Date: Thu, 22 Apr 2004 11:02:00 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040422110035.02e649c8@server-1> (raw)
In-Reply-To: <5.2.0.9.1.20040422091357.00ac3e98@imap.eco.rug.nl>
At 09:26 22/04/2004, you wrote:
>Hi all,
>
>I would like to make a flowchart in which one shape (FLOWcell) is
>essentially bigger than the other shapes (in fact it should occupy the
>space for two ordinary shapes).
>Now I made two flowcharts; one consists of the one bigger shape, while the
>other consists of the remaining shapes (of which two are invisible because
>their shape is defined as `node'). My idea is to put one flowchart on top
>of the other.
>Is this possible? And if it is, how should I do this?
>B.t.w. using `offset=overlay' in \setupFLOWcharts gives a syntax error.
\startoverlay
{... de chart ...}
{... de chart ...}
\stopoverlay
Hans
next prev parent reply other threads:[~2004-04-22 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 7:26 Sytse Knypstra
2004-04-22 9:02 ` Hans Hagen [this message]
2004-04-23 7:53 ` Sytse Knypstra
2004-04-25 22:11 ` Hans Hagen
2004-04-26 11:25 ` Sytse Knypstra
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=6.0.1.1.2.20040422110035.02e649c8@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).