Re: Query to get values for Attributes, posted by Andreas Luedeke on Mon Sep 21 20:03:49 2020
|
That would be a nice feature...
If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get
HTML source code that provides you with all possible attribute choices. |
Re: moving eLog to another computer, posted by Andreas Luedeke on Sat Oct 3 11:08:27 2020
|
you need to copy your logbooks into the "logbooks" directory.
you need to copy your elog.cfg logbook config file to the
new elog folder and reference it at start-up (something like "elogd -c /usr/local/elog/elogd.cfg ...")
Some people modify other
stuff (CSS, java scripts) but if you had you would know what you did. |
|
Re: Field values dependent on other selections, posted by Andreas Luedeke on Fri Oct 23 15:10:54 2020
|
Instead of using three different options you could use the same:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Form = 5mm, 20mm, 30mm |
|
Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 17:07:00 2020
|
You could transform your entries into the ELOG file format (either XML or CSV) and then use the import function. That would upload the correct dates
from your entries.
If you use the "Orig Date" trick you've proposed, you'll see that datetime fields are stored as seconds of the epoch (since |
|
Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 21:59:03 2020
|
Hi David,
correct. And in addition you will need to convert "Orig Date" from seconds-of-the-epoch into a properly formated date string (see example
below from Stefan) ... |
|
Re: Change / List Change doen't work anymore?, posted by Andreas Luedeke on Tue Dec 1 22:57:25 2020
|
[quote="Harry Martin"][quote="Harry Martin"][quote="Stefan Ritt"][quote="Holger Mundhahs"]Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my |
|
Re: Date conversion, posted by Andreas Luedeke on Tue Feb 23 17:20:39 2021
|
If you define a field as "datetime" then you'll get the standard ELOG input field for datetime. It will be stored as seconds of the epoch
(seconds since 1.1.1970).
You can define a field as a default string input, then it is stored as a string. But you can convert that string by a shell scripts into seconds |
Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 14:56:12 2021
|
Hi Stefan,
I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command. |