Subst TotalRisk = $shell(echo $Risk1 + $Risk2 + $Risk3 > /tmp/elog_out)

Subst <attribute> = $shell(gawk 'BEGIN{ print $Attrib1 + $Attrib2 + $Attrib3 }' ) 

Maybe it is a wrong configuration, because in this forum it works well.
If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
and after clicking OK the entry is closed. Because this behavior is on all loggbooks
it must be a global config entry, but I dont know, which.
Here is the GLOBAL section:

Expand Selection page = 1
URL = http://sapelogs/
Date Format = %d.%m.%Y
Time Format = %d.%m.%Y %H:%M
Reverse Sort = 1
Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Copy to, Config, Admin, 
Login, Logout, Help
Find Menu commands = New, Edit, Delete, Reply, Download, Find, Last day, Last 10, Select, Config, Admin, Login, 
Logout
Password file = passwords.txt
Login expiration = 2
Admin user = ME
Suppress Email to users = 1
Self register = 0
Logout to main = 1
admin textarea = 150,45
Entries per page = 100
Mode commands = 1
Use Lock = 1
Supress Email on edit = 1
Supress default = 1
Summary lines = 1

Icon comment log.gif = Allg. Log
.....
Group SAP = .....

> Maybe it is a wrong configuration, because in this forum it works well.
> If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
> and after clicking OK the entry is closed. Because this behavior is on all loggbooks
> it must be a global config entry, but I dont know, which.
>
> ...
> Use Lock = 1
> ...

I comes from using the lock. If you remove that, you won't get this dialog box any more.

> > Maybe it is a wrong configuration, because in this forum it works well.
> > If I change the encoding in the logbook entry I get "Submit modified ELOG entry?",
> > and after clicking OK the entry is closed. Because this behavior is on all loggbooks
> > it must be a global config entry, but I dont know, which.
> >
> > ...
> > Use Lock = 1
> > ...
> 
> I comes from using the lock. If you remove that, you won't get this dialog box any more.
OK, it seems, that the last part of the Use Lock documentation is the explanation:
----
If someone edits an entry, but then goes away from that page or closes the browser without submitting the 
changes, a pop-up window appears asking the user to submit the changed entry. Although this works for most 
browsers in most cases, it could be that Javascript has been turned off in a browser, in which case the stale 
locks still might appear.
---
So if I switch the encoding the whole entry is reloaded, and the JS take it as leaving.
Is it possible to change this behavior? Changing encoding should be handled different as
"regular" leaving.

Additional information:
If you have set Use Lock = 1 you can't switch the encoding on a NEW entry.
The new entry is closed w/o saving. To prevent this you must input any data,
after them you can save the NEW entry with the PopUp-OK. But there can't be 
anyone else on a new entry?

> So if I switch the encoding the whole entry is reloaded, and the JS take it as leaving.
> Is it possible to change this behavior? Changing encoding should be handled different as
> "regular" leaving.

I fixed that in the current SVN version.

Could you implement a 'hide attribute' and 'sort attribute' config option?
While sort is probably not so easy to do the hide option would already 
be very useful.  What I want to do is to use elog to collect bibtex entries
which are then used to generate a bibtex file.  So, e.g. if the entry 
type 'Article' is selected I would like that all fields that do not make
sense are hidden.  Currently I just lock them.  The config looks like
this:

Attributes                  = Login, Bibtex Key, Entry Type, Address,
Annote, Author, Booktitle, Chapter, Crossref, Edition, Editor, Howpublished,
Institution, Journal, Key, Month, Note, Number, Organization, Pages,
Publisher, School, Series, Title, Type, Volume, Year, URL, Short Comment
Options Entry Type          = Article{1}, Book{2}, Booklet{3}, InBook{4},
InCollection{5}, InProceedings{6}, Manual{7}, MastersThesis{8}, Misc{9},
PhDThesis{a}, Proceedings{b}, TechReport{c}, Unpublished{d}
Required Attributes         = Entry Type
; ARTICLE
{1} Comment Author          = [required]
{1} Comment Journal         = [required]
{1} Comment Title           = [required]
{1} Comment Year            = [required]
{1} Locked Attributes       = Address, Annote, Booktitle, Chapter, Crossref,
Edition, Editor, Howpublished, Institution, Key, Organization, Publisher,
School, Series, Type


Instead of Locking the attributes, hiding them altogether would make the
entry form look much nicer.  
A further improvement would be to sort the attributes, e.g. for author I
would sort the like this, i.e. the more important entries first:

{1} Sort Attributes    = Author, Title, Journal, Volume, Pages, Year, Month,
Number, Note

Attributes not mentioned in the sort line could then be displayed 
in any order. 

> Could you implement a 'hide attribute' and 'sort attribute' config option?

I implemented it as 'hidden attributes = <list>' and 'sort attributes'.

> > Could you implement a 'hide attribute' and 'sort attribute' config option?
> 
> I implemented it as 'hidden attributes = <list>' and 'sort attributes'.

'sort attributes' sorts the logbook entries when they are displayed.  Or?

What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
should be listed first, as they are required for this bibtex entry type.
Is it possible with the current elogd version to also sort (rearrange) the 
attributes in the entry mask?  If yes, how?  

Thanks for your time.

> 'sort attributes' sorts the logbook entries when they are displayed.  Or?

Right

> What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> should be listed first, as they are required for this bibtex entry type.
> Is it possible with the current elogd version to also sort (rearrange) the 
> attributes in the entry mask?  If yes, how?  

Attributes are shown in the order you specify them in the config file, so what about

Attributes = Entry type, Author, Journal, Title, Year     ???

> > 'sort attributes' sorts the logbook entries when they are displayed.  Or?
> 
> Right
> 
> > What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> > selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> > should be listed first, as they are required for this bibtex entry type.
> > Is it possible with the current elogd version to also sort (rearrange) the 
> > attributes in the entry mask?  If yes, how?  
> 
> Attributes are shown in the order you specify them in the config file, so what about
> 
> Attributes = Entry type, Author, Journal, Title, Year     ???

Because for 'Entry type'='InProceedings' one needs:
'Author', 'Title', 'Booktitle', 'Year', 'Volume', 'Number'.
So, depending on the entry type that was chosen the entry mask should change,
with the required fields first and the not valid fields should not be shown
at all, which can nicely be done with the 'hidden attributes' config option.
Only the sorting (of the entry mask!) is missing! :)

> Only the sorting (of the entry mask!) is missing! :)

Ok, I put that on my wish list. So once the second or third person asks for it, I will
implement it (;-)

> > Only the sorting (of the entry mask!) is missing! :)
> 
> Ok, I put that on my wish list. So once the second or third person asks for it, I will
> implement it (;-)

I'm asking! :-)

I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them 
in. So that when you select the drop-down box, alle options are sorted.


Lars

> > > Only the sorting (of the entry mask!) is missing! :)
> > 
> > Ok, I put that on my wish list. So once the second or third person asks for it, I will
> > implement it (;-)
> 
> I'm asking! :-)
> 
> I have a few Extendable Options attributes, and it would be extremely nice if they got sorted as users put them 
> in. So that when you select the drop-down box, alle options are sorted.
> 
> 
> Lars

Agreed - that would be nice