Is it possible to visually group attributes with border, posted by Daniel Sajdyk on Thu Oct 8 12:29:55 2020 
|
Hello,
I'm working on new logbook and in one category I'll have many attributes (many more than in attached screenshot).
So here is my question. Is it possible to visually group such attributes with some border, or something like that? |
|
Up-to-date windows-version, posted by Sergei Gavrilov on Sun Oct 18 16:59:38 2020
|
Dear colleagues,
Can someone compile an up-to-date windows-version or write a manual how to do it in Windows without compiling errors?
Thank you. |
|
From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 15:08:17 2020
|
I'm running Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload
all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit
not allowed. |
|
Upload attachment with py_elog, posted by Bruno Schuler on Tue Oct 20 16:05:40 2020
|
Hello,
How can one add an attachment to a new or existing entry with py_elog?
E.g. if I want to upload an image. |
|
MEG style elog configuration, posted by Daniel Kohl on Sun Oct 25 06:26:49 2020
|
Hello,
I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to |
|
Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:00:03 2020
|
I'm converting our on-call logbook, with 25 years of history, to elog. Is there a way to override the current date/time for the Date field with the
creation date/time of the original logbook entry? |
|
Placeholders in Python API, posted by Florian Feldbauer on Wed Nov 25 15:10:34 2020
|
Hey all,
In the configuration of the Elog one can use
Preset Author = $long_name |
|
length of condition names, posted by Harry Martin on Wed Dec 2 22:45:16 2020
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change
to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive |