Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parts editor needs to be able to save a new VERSION of a file (not a whole new part) #2907

Open
davidperrenoud opened this issue Aug 26, 2014 · 1 comment

Comments

@davidperrenoud
Copy link
Contributor

From bitsybof...@gmail.com on January 30, 2014 23:52:52

With the need to change schematic images this has become more of a problem.

Open part with bad schematic image, load new image for schematic, assign pins etc, and select to Save.

You are prompted for a prefix and the part is saved in a new file, as a different variant ("variant 2"), so now you have both the crusty old part and the new hotness part both in your bins, effectively different parts.

This is not desirable in any way I can think of.

There needs to be a way in the parts editor to

  1. change the version string (X)
  2. force it to save the part without creating a whole new part file, that is, force the parts editor to write to a specific file (the same fzp you opened, or any other file location you want to write it to).

Original issue: http://code.google.com/p/fritzing/issues/detail?id=2909

@Halli50
Copy link

Halli50 commented May 11, 2015

Version 0.9.2 (beta) - new parts editor - no longer creates new .fzp's when simply saving a part.
It does, however, create 4 new .svg's every time you save a part (one for every view), which is extremely frustrating.
2.
The apparently random 32 character hex string "suffix" included in every part filename is also extremely annoying. One would think that the new serial number at the end of each part filename should do the trick of distinguishing new versions of a part. There may be some obscure reason for this extra random part of the filename, but why a full 32 character hex string? One would think a 2-4 character random hex string would do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants