X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	geda-user AT delorie DOT com
From:	Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject:	Re: [geda-user] gschem edits vanishing
Date:	Tue, 24 Mar 2015 03:37:57 +0100
Lines:	27
Message-ID:	<meqim6$d7k$1@ger.gmane.org>
References:	<550D5F43 DOT 7020501 AT earthlink DOT net> <1427055675 DOT 10088 DOT 11 DOT camel AT cam DOT ac DOT uk> <20150323185439 DOT GA2429 AT localhost DOT localdomain>
Mime-Version:	1.0
X-Complaints-To:	usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	a89-182-91-155.net-htp.de
User-Agent:	KNode/4.14.1
Reply-To:	geda-user AT delorie DOT com

Vladimir Zhbanov wrote:

>> gschem's file format is very very simple, so the behaviour you
>> describe I think will turn out to be due to a mistake such as I
>> described above, or some inadvertent copying of an out of date
>> backup file.
> 
> ... and using a CMS helps to avoid such mistakes.
> 
Automatic commit at every save?

Other applications do either: 

a) implement some kind of locking. Only one instance of the 
application can open a document at a time. This is kind of old style. 
It is prone to irritate users with stale lock files in case an 
application is not closed properly for some reason. MS-Word is/was 
infamous for this.

b) detects changes of the file in the file system and make sure the 
user does not accidentally overwrite with a new save. If pcb sees a 
third party change of the currently open file it present a big orange 
beam on the top of the window and asks what to do -- reload or 
continue working on the old version. This greatly reduces the chance 
to unknowingly mess up intended changes with a save.

---<)kaimartin(>---

- Raw text -