Repository navigation
Replies: 1 comment 1 reply
|
Are people really co-working on files by putting them on a shared drive? That sounds crazy dangerous. I am used to check out / check in procedures. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When two people open the same project from a shared drive, nothing warns either of them. Both can edit, and whoever saves last silently overwrites the other's work. QElectroTech already stops you opening the same file twice in one window, but not across two PCs, two users or two running copies.
We propose two small changes. Neither changes the
.qetor.qetzfile, so older versions open everything as before.1. Check before saving. QElectroTech remembers the file's date and size when it opens the project. If they have changed by the time you save, it asks: "Someone else saved this project at 10:04: Save as a copy / Overwrite / Cancel". This also covers older versions and shares that lose the lock file.
2. A lock file next to the project. A small hidden file (
.~motor.qet.lock) says who has the project open, on which PC and since when. It is refreshed every minute and removed on close. The next person sees "Opened by Alex on WORKSHOP-PC since 09:12 (active 1 min ago)" and chooses Open read-only (the default), Open anyway (for a lock left behind by a crash) or Cancel. Read-only uses the existing read-only mode. Exports and scripts from the command line never stop at a dialog. A folder you cannot write to opens read-only, as it does today.Qt's own
QLockFilecannot be used as it is. A lock taken on another PC counts as abandoned after 30 seconds, and the file does not record a user name.Later, editing together. The lock file holds a list of what is locked, starting with "the whole project". Later it could hold single folios, plus a lock on the whole project for jobs like renumbering wires, which change every folio a wire crosses. EPLAN and AutoCAD Electrical work this way.
.qetzalready stores one file per folio, so it can grow into this. A single.qetfile cannot. Nothing here builds that part.Questions:
All reactions