From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Flowcharts
Date: Fri, 17 Sep 1999 14:11:20 +0000 (GMT) [thread overview]
Message-ID: <14306.19465.87310.611504@PC709.wkap.nl> (raw)
Hi all,
Some footnotes to the almost new m-chart module and its documentation.
I just spend a couple of hours playing with it, and noticed some
peculiarities that were not completely obvious from the documentation,
as well as a rather nasty problem with texexec:
- texexec does not recognize the fact that flowcharts should always be
run twice if the setup parameters change (discovering this took me a
very long time)
- Just about very command within a cell is required
- All flowcharts are pre-defined using the buffer mechanism
- I'm not sure I understand the relations between setup params
width= and maxwidth=
- It should probably be documented that dx= and dy= refer to the
distance between the text and the cell boundaries (I still not
completely certain what exactly they control, but they have an
affect on the font size that, for me, was a complete surprise)
- maxwidth= is not mentioned in the \setupFLOWcharts summary
Well, once I figured out this documentation, it worked perfectly.
Hans, thanks!
Greetings, Taco
next reply other threads:[~1999-09-17 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 14:11 Taco Hoekwater [this message]
1999-09-17 12:39 ` Flowcharts Hans Hagen
1999-09-17 14:59 ` Flowcharts Taco Hoekwater
2004-11-17 14:18 FLOWcharts Nikolai Weibull
2005-03-11 15:56 FLOWcharts Adam Duck
2005-03-13 21:57 ` FLOWcharts Willi Egger
2005-03-16 9:20 ` FLOWcharts h h extern
2006-09-21 9:53 FLOWcharts Adam Duck
2006-09-21 18:23 ` FLOWcharts Willi Egger
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=14306.19465.87310.611504@PC709.wkap.nl \
--to=taco.hoekwater@wkap.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).