I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?
Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.
Endless thanks for this product and all your work Stefan.
| Stefan Ritt wrote: |
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|