Peter Rolf wrote:

Johan Sandblom schrieb:

...

What would be the drawback of allowing

backgroundcolor=n imply background=color

and

backgroundscreen=x imply background=screen

in the setup to \framed. Background compatibility should not be an issue and I am failing to imagine cases where it would not be desirable.

The background parameter is not fixed to 'color' or 'screen'. You can use any type of overlay background (which itself can use the parameter backgroundcolor). So the usage of 'backgroundcolor' doesn't always imply 'screen=color'. At least not in my macros.. :)

is anyone using screen? deep down it's already mapped onto color anyway (the color mechanism will reduce colors anyway) .. if not, we might as well remove it from mkiv Hans ps. it dates from the time where not all printers could print gray areas and fallbacks were needed (fakes, real old code often) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Johan Sandblom schrieb:

So perhaps as expected it turns out that the limitation was only in my imagination. Thanks for the responses.

Johan

2008/9/2 Hans Hagen :

...

Peter Rolf wrote:

...

Johan Sandblom schrieb:

...

What would be the drawback of allowing

backgroundcolor=n imply background=color

and

backgroundscreen=x imply background=screen

in the setup to \framed. Background compatibility should not be an issue and I am failing to imagine cases where it would not be desirable.

The background parameter is not fixed to 'color' or 'screen'. You can use any type of overlay background (which itself can use the parameter backgroundcolor). So the usage of 'backgroundcolor' doesn't always imply 'screen=color'. At least not in my macros.. :) is anyone using screen? deep down it's already mapped onto color anyway (the color mechanism will reduce colors anyway) .. if not, we might as well remove it from mkiv

I can live without (and it's not a big deal to get the same effect with a slightly different setup). So if it doesn't hurt too much, cut of the

It's limited by your main focus. The drawbacks of specialismn (mine is graphics, so I surely lack the textual part [not always (some would say most times) aware of it]) :D old pigtails. *ConTeXt is a democratic kingdom* ;) Regards, Peter

...

Hans

ps. it dates from the time where not all printers could print gray areas and fallbacks were needed (fakes, real old code often)

must be from the time before I was born (or realized what a printer is) ...

...

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________