> BTW,
> Is there any way to turn off the Text column at the right side of the list?

Summary lines = 0

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

"Find menu commands" apply to the LIST of entries, while "Menu commands" apply
to the page where a SINGLE entry is shown. I know that "Find menu commands" is
a misleading name, but it's historical, I should change it to "Menu commands"
and change the other to "Entry menu commands", does that make more sense?

> > Is there any way to configure elog so that attribute fields can be edited 
> > on more than line like the 'text' field? 
> > 
> > (This would be useful so that attributes could contain larger portions of 
> > text including line breaks)
> 
> No, but this request is already on the wishlist
> (http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.

Stefan,

Was just wondering about the status of the multi-line attributes in Elog, are 
they implemented in elog yet? If not is that something you are planning to do 
in the future?

many thanks

Paul

> Was just wondering about the status of the multi-line attributes in Elog, are 
> they implemented in elog yet? If not is that something you are planning to do 
> in the future?

In order to have multi-line attributes, the whole format of the logbooks has to be
changed. I plan to use XML for the logbook format in the future. We would not have
any more one file per day, but one big file per logbook. I have already some XML
functionality in elog, but this one requires a major rewrite of the whole code. On
the other hand, searching etc. will become much faster afterwards. I plan to start
this development soon, but it might take quite some time, so don't expect it
before summer or fall.

Best regards,

  Stefan

> > Was just wondering about the status of the multi-line attributes in Elog, are 
> > they implemented in elog yet? If not is that something you are planning to do 
> > in the future?
> 
> In order to have multi-line attributes, the whole format of the logbooks has to be
> changed. I plan to use XML for the logbook format in the future. We would not have
> any more one file per day, but one big file per logbook. I have already some XML
> functionality in elog, but this one requires a major rewrite of the whole code. On
> the other hand, searching etc. will become much faster afterwards. I plan to start
> this development soon, but it might take quite some time, so don't expect it
> before summer or fall.
> 
> Best regards,
> 
>   Stefan

Thanks for your help, thats useful to know.

Paul

> > Is there any way to configure elog so that attribute fields can be edited 
> > on more than line like the 'text' field? 
> > 
> > (This would be useful so that attributes could contain larger portions of 
> > text including line breaks)
> 
> No, but this request is already on the wishlist
> (http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.

Hi Stefan, could you add my vote for this feature too please?

Many thx

Hello,

I am currently using ELOG as a daily logbook for work performed for customers.  This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.  

Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf.  This process all works fine, mostly, except I run into the following obstacles (that are all human related.)

1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.

2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed.  For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.  

2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.

2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log).  ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.

All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.

To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later.  This would serve as sort of a place holder.

However, I can't commit myself to always create a log entry for every day either.  Again, human error.

Is what I would like to be able to do is create a new log entry, every single day, automatically.  I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.

My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc.  Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.

Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?

Thank you very much in advance!