Have tried to use "Menu commands =" to list menu commands available as per:
"Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"

but it does not seem to work; with command above I get default menu 
structure.

Using:
"Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
HELP"

I get the menu I want.
Q what's the difference?????

> > Have set up 3 top level groups, each with their own password file.
> > Ever since users have to 'login' twice to get to the appropriate elog.
> > You click on top level group, get to log book and click on the one you 
want 
> > and get login/password dialog box, click ok and and you get it again 
and 
> > then you finally get into the elog book.
> > 
> > Anything I can check on this behavior?
> 
> Sorry my late reply, was very busy these days... (;-) Can you send me your
> elogd.cfg so that I can see how you defined your groups?
> 
> - Stefan

OK elogd.cfg is attached.

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

> > '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! :)

> > > Playing with all the configuration possibilities I have one issue:
> > > I like to use the "Extendable options" but I can't combine them with 
> > > the "Conditional attributes".
> > 
> > That was never ment to work. But I found some time to implement it. If you
> > download elog255-4.exe from today it whould work. Let me know if you have
> > problems.
> 
Hello Stefan,

the changes I asked for, are working as requested. The extandable options are 
inserted into the correct line of the conditional attributes. 

  Thanks.

PS: While testing on a new demo logbook, I first made the mistake to declare 
both options, the first one and the related one as extendable. But I can imagine 
that this was really never ment to be implemented.

> '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     ???

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

If an attribute uses MOptions and is also extendable, clicking "Add 
<attribute name>" and entering a value adds the value to the MOptions, but 
does not put the value into the log entry. The log record has that 
attribute blank.
You have to go back into the record and edit it to put the new value in.