Thanks Stefan,  Downloading shortly and I'll let you know ;-)
> > Hi Stefan,
> > 
> > When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> > the entries' ID number(s) ($@MID@$).  While it may not be good practice, we've referred to these numbers in
> > cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> > your FAQ about marking of whole threads).
> > 
> > In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> > ID number.
> > 
> > Thanks,
> > 
> > David Pilgram.
> 
> I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the 
> configuration. I have not tested this extensively, but I'm sure you will do it ;-)

> > Hi Stefan,
> > 
> > I don't know if anyone else would be interested or need this...
> > 
> > If you have an Roption, and it is not required (maybe...) or have a preset attribute, it is possible to make an
> > entry and have replies without any of the attributes in that Roption being selected.
> > 
> > However, once an attribute in that Roption has been selected, it is not possible to go back (editing) to the
> > condition before one was selected on that entry (so far as I can tell).  
> > 
> > Is a way of cancelling all the possible attributes in an Roption practical?  Would others want it?  It is
> > possible with options, as there is a "please select" which can be used to cancel whichever attribute in the
> > option that has been selected.
> > 
> > Regards,  David
> 
> The easiest to achieve this is to define another option. Assume you have the three options
> 
> One, Two, Three
> 
> and you want to "unselect" them. So just add a fourth option like
> 
> Unspecified, One, Two, Three
> 
> so if you do not want any of the "One, Two, Three", just click on "Unspecified" and you get what you want.

This is sort of what I do now, I just wondered if there was a way of clearing that would leave the field completely
blank in the YYMMDDa.log file.

Thanks.

 2244 is now running, and indeed, the "Size" attribute works now. Thank you!

By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good!

 Sorted no problem

 Have fixed this by removing the last added user from the Passwd file.

 Have fixed this by removing the last added user from the Passwd file.

> > Hi Stefan,
> > 
> > I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> > images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> > 
> > The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> > attached as expected.
> > 
> > Is this correct, or a defined limitation?
> 
> This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up 
> with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.

Thanks, Stefan (why is this answer down under my name!?)

I couldn't find reference to this in the documentation.  In the case I referred to, I'll have to play with the pdf so that
the six pages I actually want displayed are.