A limited message width does not make sense for HTML or ELCode encoding since the text is laid out by the browser dynamically when displaying messages. For example have a look at this very message in your browser, and resize your window. You will see that the text flows dynamically, so the line breaks move with the window size. Furthermore the text entry uses a variable width font, so a fixed line length would not result in line breaks at the same vertical position. Therefore the message entry size scales automatically with the browser window. If you need lines with fixed length, you can only do that in plain encoding.

That is the the problem the text does not resize with the window or sending to the printer.

As I told you, if you need that feature, stick to plain encoding.

Hi,

I'm importing an Excel spreadsheet into ELOG through CSV format.  All working fine apart from dates.

Dates are exporting from Excel in the format "day/month/year" so 1st January 2008 is exported as 01/01/2008 in the CSV.

However all dates are displayed in ELOG as "01/01/1970" regardless of the field content, and looking at the raw ELOG data file dates are displayed as numeric's - so for example 01/01/2008 is "1199188800"

Can you tell me how dates are computed/stored in ELOG so that I can do the necessary conversion.

Many Thanks

Fergus

S'ok - looked up the documentation  and have converted Excel dates to ELOG 'seconds since 01/01/1970' and all has come over fine!

Thanks

Fergus

Hi,

We've defined a "LastEdit" attribute for some of our logs so that we can indicate that an entry has been revised, and when that was done. 

From our config:

Attributes =  Last Edit, etc etc
.
.
.
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date

This works fine, but when we sort the LastEdit column, the dates are sorted alphabetically. Is there a way to tell Elog to treat this particular attribute 
as a date when sorting?

> Hi,
> 
> We've defined a "LastEdit" attribute for some of our logs so that we can indicate that an entry has been revised, and when that was done. 
> 
> From our config:
> 
> Attributes =  Last Edit, etc etc
> .
> .
> .
> Preset Last Edit =$date
> Locked Attributes = Last Edit
> Subst on edit Last Edit = $date
> 
> This works fine, but when we sort the LastEdit column, the dates are sorted alphabetically. 
> Is there a way to tell Elog to treat this particular attribute as a date when sorting?

You are missing:

Type Last Edit = datetime

which will tread the "Last Edit" attribute as a date/time combination. Actually it's stored 
internally in seconds since Jan 1st 1970, so sorting will work right. The only caveat is that
when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
fix this in the next release.

> The only caveat is that
> when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> fix this in the next release.

I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
with elog, I could tell you how to upgrade.