I did know about format strings, which is why I was totally surprised that...

format DocumentArrowsTop false

... apparently does absolutely nothing. I have created another paged image test collection and re-verified this. Not only that, but removing the DocumentArrowsTop format string altogether does nothing as well! The DocumentArrowsBottom has the correct behavior, however.

Thanks for the info on the c++ code. I used to code a lot in c++. I'll have to mess with this some day. Have a great weekend...

- Gavin

>>> Michael Dewsnip <mdewsnip@cs.waikato.ac.nz> 05/17/07 10:12 PM >>>
Hi Gavin,

There are two format statements that you can use to hide the top and
bottom navigation arrows:

format DocumentArrowsTop false
format DocumentArrowsBottom false

These go in the collection's collect.cfg file.

Regarding your second question, unfortunately the layout of the document
page can't be controlled easily because this is set in the C++ code. If
you look at the do_action_html() function in
src/recpt/documentaction.cpp, you'll see it writing out:

1.

HOME HELP PREFERENCES

2.

SearchSubjectsFromDates

3. The document table of contents
4. (if enabled)
5. (if enabled)
6. The document text
7.

All the best,

Michael

--
DL Consulting
Greenstone Digital Library and Digitisation Specialists
contact@dlconsulting.com
www.dlconsulting.com

Gavin Spomer wrote:
> Does anybody know where I can get comprehensive information on the _navarrowstop_ and _navarrowsbottom_ macros and the navigation arrow buttons in general?
>
> I can't find much documentation on them and have found very little in the list archives as well.
>
> So far I have found out on my own:
>
> 1. The navarrows can only be used with paged image and html collections, right?
> 2. I can override the _navarrowsbottom_ and _gotoform_ macros, but not the _navarrowstop_ macro in my extra.dm file.
> 3. In a paged image collection I cannot remove the top arrows, period.
>
> In addition to solving the above mysteries, I'd really like to be able to move the navarrows to a different location on my document pages, but when looking at document.dm, the

oops