On Wed, 2005-08-10 at 11:37, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > I have no clear explanation for this. There could be a deeper bug behind
> > this in the way layout files are read and overlayed. Ideas?
> 
> My guess is that the counters mechanism first has to know what sections a 
> class has (stdsections definitions), before the counters for them are being 
> set (numreport.inc).

I don't think so... the layout is defined the moment a 
Style Section etc. statement appears first, i.e., in
numreport/numarticle. Even if most of the attributes ("layout tags")
still remain undefined at that point.

But that brings up another question: inspecting lyxlayout.C's
LyXLayout::LyXLayout () (the constructor), it seems that a number of
layout tags are not initialized (or rather, assigned initial values.)
Isn't this mandatory? And will we not get into trouble if some of these
are initially filled with junk?

Just wondering.

- Martin

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to