Hi John. The problem with using the Find-->Export method is that some of the Attributes for the older data are no longer shown on that screen because the Config file has since changed. That's why I'm contemplating somehow parsing the log files directly instead.

Well, you could put the old options back to the config file, do the export, then remove them again.

But have a look at the Elog database files ZZMMDDa.log in your logbook directory, they are pure ASCII files, which are relatively simple to parse.

Hi,

I had similar needs (access and parse logs ) so I'm  a small library in cpp. Have a look on https://github.com/flagarde/elogpp maybe it could be usefull for you too.

> Hello,
> 
> I've had much success and use with ELOG.  However there is one thing that I wish I could figure out in order to 
> make ELOG work exactly as I need it.
> 
> When I either create a new ELOG entry, or, have one created via an automated scrip run by CRON, the paragraph 
> width is preset. 
> 
> I've read the notes and experimented with setting the text size, but it seems that if I either adjust it via the 
> config file, or, change the size by dragging the message box itself, then I end up with an ELOG entry that has an 
> irregular message size to it than all the others.  Consistency and uniformity is very important to me for how I 
> use ELOG.
> 
> It would be idea, if the log entries did not contain <CR>'s or justified lines.  In other words, I would like to 
> be able to have my ELOG entry fill the width of the screen, be it a wide screen or standard portrait scree, and 
> at whatever resolution and text size I have my browser set to.
> 
> By not filling the entire width (and also by not having it auto adjust depending on screen size, resolution, 
> etc.) there are large portions of the screen real estate that is lost and you end up with very long, scrolling 
> log entries versus entries that file the entire width and therefor take less vertical screen space.
> 
> With all that said -- Does anyone else have this issue?  And, is there anything I can do to correct this?  This 
> would make me a very happy user if it could be done.
> 
> Thank you in advance!
Hi Ryan,

Do you quote the previous entries in later entries, with the '>' character (as above)?  I ask this because that will
make what you are requesting much more complicated, soon making those previous entries very difficult to read
indeed.

For me, readabiliy of previous quoted entries is important - along with the indenting '>' character to denote each
entry - your request would be an issue for me simply because of how many times an entry may get re-quoted in later
replies - over 40 is not uncommon.  As such, I tend to keep my lines short when writing an entry, being aware
that it could soon have a large number of '>' characters preceeding it.

[Sep 03 07:30]
Not an aside as such, but I have tried to experiment with this quoting business, to remove the '>' character (easy
enough) but have each quoted reply headed with a simple date/timestamp *within* this text box, such as I headed this
paragraph.  It hasn't worked as I expected, and I'm not sure why - maybe it might even be a bug!  But if that
could be cracked, then your suggestion would be a boon to me as well.
 

I may have made this sound as if the issue occurs if the first entry in a thread has an attachment; in fact it
happens whether or not there is an attachment to the first entry.

Hope this makes matters a bit clearer.


> Hi Stefan,
> 
> I must have seen this before, but only just "noticed" it.
> 
> If you attach a picture or pdf to the first entry in a tread, there is then a paperclip after the thread display
> line.  This shows up in threaded view or collapsed threaded view.
> 
> If you then attach a picture or pdf to a subsequent entry, the paperclip icon does not show up in threaded
> display, (it is still there on the initial entry) but if the attachment is to the latest entry it shows up in
> treaded collapsed display (collapse on last=1, of course).  If collapse on last=0, then initial entry shows on
> threaded, collapsed, and that has the icon as expected.
> 
> When the icon does show, you can click on it and get the correct attachment to show/launch reader or whatever.
> 
> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).
> 
> (sorry about the first posting, hit the wrong key sequence in error)
> 
> Regards,
> 
> David Pilgram.

> It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> other than the initial one).

Yes, that's indeed a bug. I fixed it in SVN revision 2266.

Thanks Stefan!

(But I'll wait and see if you do anything about Steve's point...so I'll download "after work"!).

> > It would appear to be a bug that the attachment icon does not appear in the threaded display (for any entry
> > other than the initial one).
> 
> Yes, that's indeed a bug. I fixed it in SVN revision 2266.

There is only an open source version.