ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: shading box many times
Date: Tue, 29 Nov 2005 14:14:30 +0100	[thread overview]
Message-ID: <438C5436.7070303@seznam.cz> (raw)
In-Reply-To: <438C185B.5060903@wxs.nl>

Hans Hagen wrote:
> Vit Zyka wrote:
> 
>> Hans Hagen wrote:
>>
>>> Taco Hoekwater wrote:
>>>
>>>> Hans Hagen wrote:
>>>>
>>>>> Vit Zyka wrote:
>>>>>
>>>>>> Dear Metafun Wizards,
>>>>>>
>>>>>> I have noticed some strange behaviour with box shading. It works 
>>>>>> OK until some number of shadings. Please see example:
>>>>>>   http://typokvitek.com/tmp/shade-many.pdf
>>>>>> Any idea for solving? Next not-minimal but small and illustrative 
>>>>>> example can help.
>>>>>
>>>>> works ok here; since it concerns independent mp runs, i cannot 
>>>>> imagine what goes wrong; mayeb a bad random numer; does your log 
>>>>> say something?
>>>>
>>>> My results are the same as Vit's example: The last 9 items are
>>>> not shaded but have 3 black sides and 1 white one
>>>> (with \write18 disabled, using a single \jobname-mpgraph.mp)
>>>>
>>>> I don't know what is going, but at least I can reproduce the problem.
>>>
>>> it's related to the fact that there can be 1000 specials only (this 
>>> /1000 in mp-spec)
>>>
>>> if you add:
>>>
>>> \def\MPrgbnumber#1{\expandafter\doMPrgbnumber#10000.00000\relax}
>>> \def\doMPrgbnumber#1.#2#3#4#5#6\relax{#2#3#4#5}
>>>
>>> \startMPinclusions
>>> _special_div_ := 10000 ;
>>> \stopMPinclusions
>>>
>>> to the file, and change all 1000's in mp-spec.tex into _special_div_ 
>>> it works ok; so, the question (for taco is): does mp have the right 
>>
>>
>>
>> Really? Hmmm, not for me. I have got the graphics with flat color per 
>> picture; every picture in the sequence has lighter and lighter color 
>> (starting from black). (After performing your instructions in the 
>> mp-spec.mp and refreshing metafun.mem.)
> 
> 
> can you try the experimental zip i posted yesterday (.../temp/cont-tmf.zip)
> forget about the definitions, just set \settrue \manyMPspecials in your 
> file
> 
> should work
 >
 > Hans

yes, it works!

Now it works even on my old distrib also. Seems the crutial line was
inside this vardef:

vardef add_special_signal = % write the version number
   if (length _global_specials_ <> 0) or (length _local_specials_ <> 0) :
     special ("%%MetaPostSpecials: 2.0 " & decimal _special_signal_ & " 
" & decimal _special_div_) ;
   fi ;
enddef ;

Again many thanks, Hans
Vit

  reply	other threads:[~2005-11-29 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28  9:02 Vit Zyka
2005-11-28 11:16 ` Hans Hagen
2005-11-28 12:36   ` Taco Hoekwater
2005-11-28 13:38     ` Vit Zyka
2005-11-28 16:37       ` Peter Rolf
2005-11-28 13:56     ` Hans Hagen
2005-11-28 14:45       ` Taco Hoekwater
2005-11-28 15:43         ` Hans Hagen
2005-11-29  0:35       ` Vit Zyka
2005-11-29  8:59         ` Hans Hagen
2005-11-29 13:14           ` Vit Zyka [this message]
2005-11-29 14:42             ` Hans Hagen
2005-11-28 13:02   ` Vit Zyka

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=438C5436.7070303@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --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).