Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!

Thanks alot Stefan, I will try it right away !!

Andreas, I really like the idea of hiding attrib 1 and attrib2 and fill attrib3 with a script (I guess using elog.exe command line) ?
I play a little with it and I can modify an attribute with the command line but I cant figure how to set the cell style based on the attrib2 and 
replace attrib3 value with attrib1 value... (basicially I need help !!!) do you think you could help me ?

> Wow !!! Im impressed :):):) I didn't expect such a fast reply !!!
> 
> Thanks alot Stefan, I will try it right away !!
> 
> Andreas, I really like the idea of hiding attrib 1 and attrib2 and fill attrib3 with a script (I guess using elog.exe command line) ?
> I play a little with it and I can modify an attribute with the command line but I cant figure how to set the cell style based on the attrib2 and 
> replace attrib3 value with attrib1 value... (basically I need help !!!) do you think you could help me ?

The downside of a script is, that it needs to execute on the server: you need to have the proper syntax for the shell of your operating system.
Here's a little example for a bash shell script, just to give you an idea (that would be for Linux, I have no experience with Windows):

Allow HTML = 1
Attributes =  person, mood, color
Default encoding = 2
Options person = John, Bill, Kate
Options mood = calm, upset
Subst color = $shell(if [ "$mood" == "calm" ] ;then echo "green"; else echo "red";fi)
Change person = <font color="$color">$person</font>
List Change person = <font color="$color">$person</font>
Show Attributes = person, mood
Show Attributes Edit = person, mood
List display = ID, Date, person


Disclaimer: When I've tested it locally the HTML was displayed as source. Stefan, any idea? (ELOG V3.1.0-5be245e)

On my linux box, every time I select a thread, or start a new entry etc, I see that one or many cookies are sent.

On a terminal, I get the message

Received unknown cookie "CalciumDisplayParams"

Now I do have a perl script called Calcium, (Calendar viewed through the browser) but it's definately not running now, not in any browser window, and in any case why should an action of ELOG trigger this?  I realise it may be due to an idiocyncratic set up of this box.  But in normal operation, I doubt the user would see these cookies being received.

Cookies are sent from your browser. ELOG has no influence on what the browser sends where. Probably you run your calender at the same machine where ELOG is running, so all the cookies your calender app stores in your browser are sent to ELOG as well. ELOG just complains about something it does not know, but otherwise this message can be simply ignored. Of course you can delete your cookies in your browser, but after the next call to your calendar app they will show up again.

Hi Stefan,

Thanks for the explanation.  I realised it was just an error message of no real import, but it can get irritating at times.

We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.