ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ian Lawrence <physics.rooted@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [m-chart] Focus feature
Date: Thu, 20 Oct 2011 09:43:48 +0100	[thread overview]
Message-ID: <BA7979B9-C02B-4183-A9ED-80617916AD56@gmail.com> (raw)
In-Reply-To: <08BCE5E5-FC9E-42FA-956B-6ACD8F0B0F2B@gmail.com>

Another one on flow cells:

The latest beta adds an unwanted frame around the text ' radiations that ionise', for cells like:

\startFLOWcell
	\name{episode_04_title}
	\location {1,5}
	\shape{7}
	\text[align=left]{{\bf Radiations that ionise}}
	\connection[nb,pt]{episode_05_title}
\stopFLOWcell


And I'm not expert enough to figure out another way of aligning them left…

On 19 Oct 2011, at 21:00, Otared Kavian wrote:

> 
> On 18 oct. 2011, at 23:49, Hans Hagen wrote:
> 
>> On 18-10-2011 21:32, Marco wrote:
>> 
>>> Another issue: According to the manual, “action” should be
>>> the default shape. However, when no shape is specified, an
>>> error is raised. Is it a bug?
>> 
>> fixed in next beta
>> 
>> also connection parsing is more tolerant now: "+ left - right" in addition to "lr" etc
> 
> Dear Hans,
> 
> The command 
> 	\comment[r]{blabla} 
> does not work anymore  in mkiv when using \usemodule[chart]: one gets an error message. (ConTeXt  version 2011.10.19 00:02).     
> It seems that in the file 
> 	m-chart.mkvi
> there is a typo at line 277: one finds there
> 	\do_FLOW_commment
> instead of \do_FLOW_comment. Fixing this typo eliminates the error message but the comment does not show up.
> 
> 
> Best regards: OK
> ___________________________________________________________________________________
> 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-10-20  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 19:32 Marco
2011-10-18 20:07 ` Willi Egger
2011-10-18 20:11   ` Hans Hagen
2011-10-18 20:19   ` Marco
2011-10-18 21:49 ` Hans Hagen
2011-10-19  8:42   ` Marco
2011-10-19 20:00   ` Otared Kavian
2011-10-20  8:43     ` Ian Lawrence [this message]
2011-10-20 11:31       ` Hans Hagen
2011-10-20 11:38     ` Hans Hagen

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=BA7979B9-C02B-4183-A9ED-80617916AD56@gmail.com \
    --to=physics.rooted@gmail.com \
    --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).