From: "Rogers, Michael K" <mroge02@emory.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: drawarrow and transparency
Date: Thu, 3 May 2012 12:47:04 +0000 [thread overview]
Message-ID: <40639B65-FA13-4553-8F94-C66CC69EF964@emory.edu> (raw)
In-Reply-To: <20120503123247.7592251f@sole.extra.cea.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1714 bytes --]
On May 3, 2012, at 6:32 AM, Alan BRASLAU wrote:
I believe that this is somewhat a bug with transparency under MetaFun.
For I tried the following:
\startMPcode
picture pic ; pic := image(drawarrow origin--(1cm,0)) ;
draw pic withtransparency(1,.5) ;
draw pic rotated 90 withtransparency(1,.5) ;
\stopMPcode
Here, the arrowhead is totally opaque and only the "stem"
has transparency. Something is fishy.
Alan
I noticed the same thing. I think original problem is with how an arrow is converted to PDF/Postscript drawing commands and how the color is computed when commands are combined. The only solution I can imagine is to define a new arrow macro that constructs the boundary path of the arrow and fills it (i.e., up one side of the stem, around the arrowhead, and down the other side of the stem). As far as I can tell, MetaPost/Postscript does not have commands that compute the boundary path of the region painted by a sequence of commands. (I think that computing the boundary might be a much harder problem in general than computing which points to paint. A straight arrow would be fairly simple.)
Michael
________________________________
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
[-- Attachment #1.2: Type: text/html, Size: 2671 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-03 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 15:35 Alan BRASLAU
2012-05-02 19:42 ` Marco
2012-05-03 10:32 ` Alan BRASLAU
2012-05-03 12:47 ` Rogers, Michael K [this message]
2012-05-03 14:09 ` Peter Rolf
2012-05-05 9:19 ` 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=40639B65-FA13-4553-8F94-C66CC69EF964@emory.edu \
--to=mroge02@emory.edu \
--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).