Hello!
On 30/06/2020 18.46, Jon Evans wrote:
> Give this issue a thumbs up: https://gitlab.com/kicad/code/kicad/-/issues/4763
Just some additions to this issue's desired features:
> 1. Capture the entire project state into a single backup archive (.zip file)
...including a timestamp in the
On Tue, 2020-06-30 at 09:28 +0200, jp charras wrote:
>
> For me, backups are like a accident insurance: you need them and you hope
> never use them.
>
> And about VCS use:
>
> Many good electronics guys do not even know what is it, and have never
> compiled any source code.
> Electronics
Give this issue a thumbs up: https://gitlab.com/kicad/code/kicad/-/issues/4763
On Tue, Jun 30, 2020 at 12:21 PM Diego Herranz
wrote:
>
> This possibility to save the last N backups would be useful. It is what
> Altium does more or less and it has proven useful to me in the past.
> Especially
Yes, it will use the system file rename command to rename the temp saved
file. If that system command fails, then wx will automatically attempt to
copy the temp saved file instead, and that will preserve the temp saved
file if it fails (so basically, the temp saved file will only be removed if
the
This possibility to save the last N backups would be useful. It is what
Altium does more or less and it has proven useful to me in the past.
Especially if you change your mind after 2h working on something which is
not going anywhere :)
Thanks,
Diego
On Tue, 30 Jun 2020 at 15:15, Wayne Stambaugh
Ah, I reread now what the change to save logic was and I agree, the main
reason for the current backup system is now irrelevant, assuming the last
step of copying over the file is done using system functions and not by
opening and writing the file.
On Tue, Jun 30, 2020 at 8:15 AM Jon Evans
What is the scenario that they guard against today? I claim that they
don't do this anymore.
Scenario 1:
1) Save, which succeeds
2) Do some work, but don't hit save
3) KiCad crashes
Result: data after last save is lost
Scenario 2:
1) Save, which succeeds
2) Do some work, hit save
3) KiCad
I don't think removing the current backup system before implementing a new
one is the right thing to do.
As limited and simple as it is, the current system provides valuable
safeguard against data loss on crashes that may corrupt the main save file.
And no, VCS is not a replacement, most people
Sounds like a great solution to me.
On 6/30/20 10:12 AM, Jon Evans wrote:
> JP, I agree that true backups are useful.
>
> Maybe even it is a good idea for KiCad to have a built-in backup function.
>
> I just don't think the current backup function is actually useful
> because of my first point
JP, I agree that true backups are useful.
Maybe even it is a good idea for KiCad to have a built-in backup function.
I just don't think the current backup function is actually useful
because of my first point (backups are overwritten on each save).
I would propose:
1) Remove the current backup
I find the backup files in the directory pretty annoying.
While it’s not ideal I’m willing to completely lose the backup functionality to
fix that.
I’m also fine with building a more sophisticated system to folder them (ie: one
that can handle the external files), but only if it’s going to
Last time I looked, there was rescue feature in the file menu of pcbnew, I
think. I never used it, I don't really know what it does, but I guess it
just reads the bak file.
tir. 30. jun. 2020 09.32 skrev jp charras :
> Le 30/06/2020 à 00:13, hauptmech a écrit :
> >
> > While I agree that it is
Le 30/06/2020 à 00:13, hauptmech a écrit :
>
> While I agree that it is not KiCad's job to do archival backups or version
> control, I do think that KiCad should preserve the integrity of users data
> through a crash. Even better if the work between the last save and the crash
> is also
I have found them more confusing than valuable, both when working on
projects and when teaching folks and they're curious about each of the new
files.
I guess we can be glad that the state of user backup/VCS is better now than
a decade ago! I tend to have little hope for things like that, but
Autosave is independent of the back up file.
On 6/29/2020 6:22 PM, Jeff Young wrote:
> How does the current backup file strategy interact with the autosave feature?
> If autosave works without it, that might address a lot of these concerns.
>
>
>
>> On 29 Jun 2020, at 23:13, hauptmech
How does the current backup file strategy interact with the autosave feature?
If autosave works without it, that might address a lot of these concerns.
> On 29 Jun 2020, at 23:13, hauptmech wrote:
>
>
> While I agree that it is not KiCad's job to do archival backups or version
> control,
While I agree that it is not KiCad's job to do archival backups or
version control, I do think that KiCad should preserve the integrity of
users data through a crash. Even better if the work between the last
save and the crash is also preserved and recovered on restart.
I have had to use
I'm +1 on removing the backup files completely. I can see how they might
have been useful in the past given the save behavior, but I think the
recent changes to that have made them obsolete. I am also someone who puts
all my projects into a git repo, so I have always found them annoying and
never
That save process change is what I was referring to in (2)
The old save process (in 5.1 and earlier) is:
1) Move (not copy) filename.ext to filename.ext-bak
2) Write the save to filename.ext (a new file at this point)
Our current save process (in nightlies) is:
1) Copy filename.ext to
> On Jun 29, 2020, at 12:23 PM, Jon Evans wrote:
>
> Currently, KiCad automatically creates backups of schematic and PCB
> files when you save a file.
>
[snip]
>
> In other words, I don't think this feature actually gives enough value
> to make it worth the clutter in the project folder
I find them annoying and have to add them to my gitignore's etc constantly.
They're of no value to me because I tend to save every 30 seconds or so
while working.
The *one* thing they might be useful for is guarding against kicad
segfaulting or other failures (disk full, NFS connection lost,
Currently, KiCad automatically creates backups of schematic and PCB
files when you save a file.
The logic for these backups is basically: if a file already exists
with the same name as what we are saving, copy that file to a new file
and give it the "-bak" suffix on the file extension.
These
22 matches
Mail list logo
