[sword-devel] BoM Bug in module/Beta T

Joachim Ansorg sword-devel@crosswire.org
Mon, 2 Sep 2002 20:00:27 +0200

You're right.
Let's use EnumaElish as an example as I don't have BoM.
DisplayLevel=2 displays e.g. all subentries of "Tablet I" together on one 
DisplayLevel=1 would display Tablet1/1, Tablet1/2 etc. each on a an own page.

I hope this is correct behaviour. Let me know.


> On Fri, 9 Aug 2002, Joachim Ansorg wrote:
> > Hi!
> >
> > > Barry is right that it just takes a while to load since we have to
> > > parse the entire table of contents and build tree items for every
> > > single verse in the book, which is probably quite a few for the BoM. 
> > > Testing in beta V, it works fine.  In fact it only takes about 2
> > > seconds for me to load on a P4-1.5GHz laptop (which consequently has a
> > > rather slow HD).  Eventually it would be nice to make the tree only
> > > show down to the chapter level and display a chapter at a time with
> > > this book, similar to how we do with the Bibles.
> >
> > I thought this is already possible by using the DisplayLevel=1 entry in
> > the config file!
> > At least in BibleTime it works pretty well for GenBooks.
> I just want to check, since I'm adding DisplayLevel tags to GenBooks right
> now:  did you mean DisplayLevel=2?
> DisplayLevel=1 is the default value (meaning display whatever is in the
> leaf nodes).  DisplayLevel=2 would display the next higher level (chapters
> in a BoM) and DisplayLevel=3 would show the next higher after that (books
> in a BoM).
> --Chris