>
>> As for the color-via-paremeters, I presume that we would need a way of
>> specifying global default parameters? Such that the default color can be
>> propagated down the tree.
>
> It is already possible to create parameters on a page. On any page,
> bring up the parameter dialog box and create a new string parameter,
> then save the file. The output looks something like this:
>
> %%Page: test 1
> %%PageOrientation: Portrait
> /pgsave save def bop
> <</@testparam (hello) >> begin
> 1.0000 inchscale
> 2.6000 setlinewidth 752 352 translate
>
> So it seems reasonable that one could define the default color up
> front for every page:
>
> <</p_col {0 0 0} >> begin
>
> as a replacement for "0 0 0 scb" in the definition for "bop"
> (beginning-of-page). That would be removed from the "bop" definition
> to be replaced by
>
> p_col setrgbcolor
>
> somewhere further down in the page header (after the dictionary, of
> course). Then calls to an object instance would have:
>
> <</p_col {r g b} >>
>
> to set a unique color for the instance, or
>
> <</p_col p_col >>
>
> to pass the color down the hierarchy. If you like, I can do the code
> modifications to xcircuit-3.7 to implement this, and you can merge the
> code changes in. I don't think it will be a huge amount of work.
> However, it will change the input/output format a bit, so I would like
> to have changes made to both your and my version of the code.
I'll merge anything that you do. I appreciate all the help -- Kuba
_______________________________________________
Xcircuit-dev mailing list
[email protected]
http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
