[dev-context] Local settings for frame borders

Marco netuse at lavabit.com
Wed May 23 19:05:14 CEST 2012

On 2012-05-23 Wolfgang Schuster <schuster.wolfgang at googlemail.com> wrote:

> You can replace
> […]

> BTW: Don’t you want different rules (toprulethicknes,
> bottomrulethickness etc.) for the “tight” frames?

It makes sense, yes. I added the code to the module. For my tables
the code works just fine (I don't use all the features). However, a
small test file fails miserably. The code in the current state has
several issues.

∙ The tight frames need a top/bottom…rulethickness setting,
otherwise it breaks the compilation. The values should be inherited
from the global rulethickness value if the individual rulethicknesss
are absent.

∙ Almost everything interferes with each other. See the topframes in
the table or the colorfullocalb example. It it coloured, but should
be black. I guess that's because they use the same global \framed
name space.

∙ For the tight frames the rulethickness is not taken into account
when placing the lines, which leads to strange offsets. See examples
colorfultight and colorfultightb.

These issues should be fixed before the module goes into the core.
This does not mean that *you* have to fix these issues! For me the
code works, but I guess for most other people the code will fail.

I will check how to improve the code. If anyone has suggestions or
fixes, please don't hesitate sharing them.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: meta-imp-loc.mkiv
Type: application/octet-stream
Size: 5999 bytes
Desc: not available
URL: <http://www.ntg.nl/pipermail/dev-context/attachments/20120523/bdff2a90/attachment.obj>

More information about the dev-context mailing list