Re: [NTG-context] \framed[backgroundcolor=x] might imply \framed[background=color]

2008-09-02 Thread Wolfgang Schuster
On Tue, Sep 2, 2008 at 11:27 AM, Johan Sandblom [EMAIL PROTECTED] wrote: 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

Re: [NTG-context] \framed[backgroundcolor=x] might imply \framed[background=color]

2008-09-02 Thread Peter Rolf
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

Re: [NTG-context] \framed[backgroundcolor=x] might imply \framed[background=color]

2008-09-02 Thread 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

Re: [NTG-context] \framed[backgroundcolor=x] might imply \framed[background=color]

2008-09-02 Thread Johan Sandblom
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 [EMAIL PROTECTED]: Peter Rolf wrote: Johan Sandblom schrieb: What would be the drawback of allowing backgroundcolor=n imply background=color and

Re: [NTG-context] \framed[backgroundcolor=x] might imply \framed[background=color]

2008-09-02 Thread Peter Rolf
Johan Sandblom schrieb: So perhaps as expected it turns out that the limitation was only in my imagination. Thanks for the responses. 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