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 changed the code such that editing of draft messages is always possible, even if the "edit" command is not allowed otherwise. Update is in GIT. Please check if that works at ND280.

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

Arghhhh! Guess how many people asked me for the autosave feature! I worked really hard on it (including an airplane flight to Japan!), not the next guy comes "can we disable that feature?". 

I agree that this feature has many side effects, and I have to adress one by one, but in the end the community will benefit. Think of starting a draft at one computer, and finishing at another one. Lazarus won't help you there.

Nevertheless , I added a "Save drafts" which you can set to zero. But I would rather prefer if people tell me their problems, and I fix them, instead of siletnly just disabling this feature and keeping the bugs there unresolved.

> Title says all :)
> 
> Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
> 
> Thanks :)

Quick and simple answer: No.

But please explain me what your case is. Maybe this can be done differently.

Forget scripting under Windows, this is painful and not really working. Wrong OS for that.

But have you considered conditional attributes? With this you can load different option lists straight from the elogd.cf file. Use something like this:

Attributes ..., List, Person

Options List = List A{1}, List B{2}
{1} Options Person = Person a1, Person a2, ...
{2} Options Person = Person b1, Person b2, ...

So if you choose either "List A" or "List B", you get a different set of persons. Is it that what you want?

/Stefan


> a) I couldn't make shell command to execute while elogd was running as a service (I'm running windows and $shell was just returning weird stuff ); shell script was 
> working only when I launch elogd.exe from a command line:
> 
> -elogd as a Service running the following : Subst Infographiste = $shell(dir c:\) 
> will return : Shell execution not enabled via -x flag
> 
> -modifying the Windows Service to add "-X" and running the following :Subst Infographiste = $shell(dir c:\) 
> will return : a empty attribute
> 
> -running elogd "-x" from a command line, the following : Subst Infographiste = $shell(dir c:\) 
> will return : the dir result..
> 
> (I also tried to change under witch user the service was running..)
> 
> b) I just couldn't figure how to build that script....
> 
> But that would be so nice ! I can see so many situations where I could use such a scenario (loading options from another logbook or from a txt/csv file 
> somewhere...)
> 
> Thanks,
> 
> :)

The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).

I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a workaround. I modified the elog code (committeed to bitbucket repository) to accept "" as empty text to suit your needs.

/Stefan

Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some 
JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog box you see. It's now fixed in the repository.

/Stefan


> I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
> development branch (V3.1.0-8196b81):
> 
> When I want to "Submit" a new entry, I get a javascript pop-up that asks me:
> 
> _This page is asking you to confirm that you want to leave - data you have entered may not be saved._
> 
> with the options:
> "Stay on page" or "Leave page".
> 
> The entry is properly submitted if I agree to "Leave page".
> But it is very confusing for my users: they are afraid to loose their entry text.
> 
> This problem only shows for some specific logbook configurations.
> Below is a minimal logbook configuration that shows this problem:
> if you select "entry = short", the pop-up is shown;
> if you select "entry = long", the pop-up is not shown, the entry is created immediately.
> 
> Attributes = entry, when
> Options entry = short{1}, long
> Type when = datetime
> {1} Show Attributes Edit = entry
> 
> 
> (PS: it took me several hours to boil down my 120 line configuration into four lines :-) )

> Apparently it was less work to fix than to isolate it ;-)

Well, I also spend like an hour on it.