New feature request for Options list, posted by Alan Grant on Wed Feb 20 22:24:05 2019
|
Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the
attributes in the Config file directly?
This would make it much easier to maintain a particular list that is referenced in several log books. |
Re: Unwanted double entries eg. double clicking submit button, posted by Stefan Ritt on Wed Feb 20 22:41:23 2019
|
"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately.
Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe
which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research |
Re: New feature request for Options list, posted by Stefan Ritt on Wed Feb 20 22:45:39 2019
|
I can put it on the wish list.
Alan
Grant wrote:
Is it possible to include an option in the next release to have the |
Re: Unwanted double entries eg. double clicking submit button, posted by Finn Junker on Thu Feb 21 08:51:21 2019
|
Thank your very much for your work on this - as i mentioned this is a minor issue.
Kind Regards Finn
|
Re: New feature request for Options list, posted by Andreas Luedeke on Thu Feb 28 14:56:50 2019
|
Just my two cent - I would have many very good applications for that feature:
Keep option lists identical over different logbooks.
Keep option lists identical over different applications.
Create
option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, |
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
Mirror synchronization and file servers, posted by Frank Baptista on Fri Mar 1 19:18:53 2019
|
We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each. Using the mirror
feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks. All of that
works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive. |
Re: Mirror synchronization and file servers, posted by Stefan Ritt on Mon Mar 4 13:35:13 2019
|
Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work
exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this
in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and |