> > I'd like this same facility with elog.  Now I know that it can be
> > done by (for example) in the config file preselecting one of the
> > selections on reply- or indeed one that does not exist to "clear" it, 
> > but in this case that is not the route I'd want to take every time.
> 
> What about defining an additional option "unspecified". So you have
> 
> Roptions attr = option1, option2, option3, none
> 
> Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does 
> not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.

Hadn't realised the standard was written that way.  
What you propose seems fine to me.

David.

> I'd like this same facility with elog.  Now I know that it can be
> done by (for example) in the config file preselecting one of the
> selections on reply- or indeed one that does not exist to "clear" it, 
> but in this case that is not the route I'd want to take every time.

What about defining an additional option "unspecified". So you have

Roptions attr = option1, option2, option3, none

Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does 
not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.

Hi Stefan,

Roptions, or Radio Buttons.  Do you recall that on old
radios, if you gently pressed a button you could release whichever
button was already in, without selecting the new button; in other
words no selection made.

I'd like this same facility with elog.  Now I know that it can be
done by (for example) in the config file preselecting one of the
selections on reply- or indeed one that does not exist to "clear" it, 
but in this case that is not the route I'd want to take every time.

What I'd like is a (optional) button along with all the others, which 
if you click on it, it will clear any selection for that particular Roption.  
At present, once an Roption has been selected, it will persist in all 
replies unless or until an alternative choice is made.  Alternatively, if 
no selection has been made, then there is no selection on the reply, either. 
[Unless something in the elog.cfg file].

Regards,

David.
 

When running as a windows service, you open a  Command Prompt and enter:

net stop elogd
net start elogd

that will restart the service.

Yes, exactly!
I prefer to use the elog.cfg for change my config.

But, How do you do for restar the elogd ? with Unregister ELOG server service ?

Anyway, thanks for yours answers !

Bob

Well, having two logbooks in the same subdirectory was initially a planned feature but really never worked. I re-visited this issue and made it working in the current SVN version. So the next release will contain the fix. 

Minor changes you do externally to the elogd.cfg file are reflected immediately under Windows (under Linux you have to send a HUP signal to the process to re-read the configuration). But if you make major changes like adding a new logbook, you have to restart elogd. 

 Let me report when I see this behaviour.

If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,

but the running elog is still running with the old configuration.  You have to restart elog for it to read the new config file and

use the new settings.

This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg

just after it has been saved.

The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,

and it's quickest to cut-and-paste,  change the heading, create a new directory and restart elog.

This may be completely off what is being reported.