> 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)

We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.  Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages.  So we have (up to now), had the following set of commands specified in elogd.ccfg

Menu commands = List, New, Reply, Delete, Duplicate, Copy to, Move to, Find, Help

The problem is that we now get auto-saved messages, but no ability for the user to actually go back and finish the draft message.  You can see an example of this state in this test elog

http://neut17.triumf.ca:8080/demo/

Clicking on the draft message you can see that it can't be editted.  If you try to click 'new' then edit the draft, you get the message 'Error: Command "Edit" not allowed'.  So we had zombie draft messages, until we added the edit command back; but that defeats our preference that users not mess up old messages.

In general this auto-saving seems like a useful feature.  So the ideal solution for me would be to have some mode where users could edit/finish draft messages, but where we could still disable users from editting completed/finished messages.  Ie, where we can omit 'Edit' from the menu command, but still get auto-save.

A less ideal, but perhaps simpler solution would be that if an elog has omitted 'Edit' from the menu commands, then this auto-save/save functionality is disabled so that we don't get uneditable draft messages.

[1] https://midas.psi.ch/elogs/Forum/67855

Hi again,
Hope I'm not draining to much time from you guys !

here is the scenario (fake one just to understand the logic..):
My main logbook as a Option attribute Called "Electrician availables" 
My second logbook is a list of workers and there capacities Moptions : "Electrician", "Plumber", "Genius"

So my question is:

Is it possible to load my main logbook attribute "Electrician availables" Options based on all the "Electrician" found under my second logbook ?

Thanks :)

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 ?

Indeed there was a bug when you have "Show Text = 0". I fixed that in the current GIT version. I also hide the "Preview" button if "Show text = 0" since it really makes no sense there. I made a Windows Patch 3.1.0-3 which  ontains this fix.

I only saw Andreas' edited version of the original enquiry, so I didn't see the orignal config file under discussion - so most of my previous entry is totally pointless.  Sorry about that.

Hi Francois and Andreas,

On Francois' first question, I wonder if Francois is using attrib1, attrib2... as the actual attribute names in the config file.  If this is the case, Francois, you can name attributes with suitable names in the configuration file and dictate which ones appear in the List and Threaded display modes. In the List Display, those names appear along the top row at the top of each column, which I think is what you want. 

This example of three lines in a config file (made up).

Attributes = Worker, System, Organisation, Customer, Status, Ticket

List display = ID, Date, Organisation, Customer, Worker, System, Status, Ticket

Thread display = $Ticket: $Worker. $Organisation / $Customer, ($message id).

In list display, those words ("Organisation", "Customer" etc) are those that appear at the top of each column.  In Thread Display, note how you can use punctuation.  Also (not shown here) you can colour the line in Thread Display depending on the attribute System (which is akin to your question on cell style colouring) a feature not much used in this forum, and the Icon at the beginning of the line depending on the attribute Status. 

This is in the documentation, but perhaps it's not clear to all that - apart from the system defined attributes - any word can be used as an attribute name, and that "attrib1" "attrib2" is just shorthand for "any words you wish to use as attribute names".

Otherwise, if you want a different word along the top if the column in the List Display (and also in the form for making a new entry) for the attribute that appears in that column, why not just use that different word as the name for the attribute?

On the third point, about Cell Style, it would be good for having attrubute 2 able to dictate the colour of the cell of attribute 1, and no need to show attribute 2 in the List Display.  But take your point that it can be done in a shell script.