From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/941 Path: main.gmane.org!not-for-mail From: Taco Hoekwater Newsgroups: gmane.comp.tex.context Subject: Flowcharts Date: Fri, 17 Sep 1999 14:11:20 +0000 (GMT) Sender: owner-ntg-context@let.uu.nl Message-ID: <14306.19465.87310.611504@PC709.wkap.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035391782 28467 80.91.224.250 (23 Oct 2002 16:49:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:49:42 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:941 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:941 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