Bend points are broken after save / crash-restore #3115

Closed
thijs opened this Issue Jul 13, 2015 · 14 comments

Projects

None yet

7 participants

@thijs
thijs commented Jul 13, 2015

bend-points-broken

Today I've twice returned to a project to find all the bend points in my traces broken. See the screenshot above. The problem is not just visual, see below:

bend-points-broken-copper

When I try to move the bend points the traces seem to have been doubled up multiple times on each other and everything gets even more screwy. So the only option is to delete all traces and start over.

I've now seen this twice, as I said. Once after choosing to restore after a crash, once after just a regular save and then opening the project again later in the day.

The version I'm using is 0.9.2 on linux.

@ubenedix
ubenedix commented Aug 5, 2015

Same problem.
Reopend files are scrap.
Moving bend points leads to chaos.
1: file reopend -> broken connections everywhere
2: moved bend point at broken connection: bend point not common to 2 traces
3: moved bend point at "C5" just a little bit to left -> "even more screwy":
I only had to touch 2 point to get from 1 to the chaos in 3.
This makes frizzing 0.9.2 ... well, unhelpful.

frizzing-fehler1
frizzing-fehler2
frizzing-fehler3

@OnkelDittmeyer

Same issues with Fritzing 0.9.2 under OS X10.9.5

@gepd
gepd commented Dec 1, 2015

I'll let here this gif to undertstand better this problem.

bug1

@aknoerig
Member

A quick heads up to everyone experiencing this bug: Jonathan has made great progress on it in the "crossed" branch (https://github.com/fritzing/fritzing-app/tree/crossed). The bug will be fixed from 0.9.3 on, and will also fix 99% of all broken files created with earlier versions.
Thanks for all the insights you provided!

@gepd
gepd commented Jan 25, 2016

Excellent news, I've been waiting long for it! :)

@aknoerig
Member

Fixed and pushed in 12b7894

@aknoerig aknoerig closed this Jan 28, 2016
@crazymadprofessor

Same issue using Maveriks,
Yesterday I been doing a PCB project for 7 hours non-stop, Today morning when I opened my project I realized that my project was usefulness , and if I try to rectify the wire routing, my project get chaotic.

Is it there any solution?
Is there some way I can fix that problemt?

Thank you very much

@aknoerig
Member

Sorry that this nasty bug has hit you, too. Expect a release of the new fritzing version in the next few weeks. It has the bug fixed, and will also repair old broken files.

If you don't want to wait, you can try building the latest version yourself, but that's a few hours work: https://github.com/fritzing/fritzing-app/wiki/1.-Building-Fritzing

@crazymadprofessor

Hey thank you very much , just I read your mail .

When my project on fritzing crashed I stopped for a while, and experimented with eagle and other softwares, but to be honest are not the same than fritzing, the workflow in fritzing is much faster and much more intuitive than other freewares . you done a really good job . Actually I don't have to much money , but definitely if I could start to work with fritzing again I will try donate some to this fantastic project.

Thank you so much for all the effort.

Regards

@mearsy
mearsy commented Mar 7, 2016

Any idea when 0.93 will be on the main site for download?

@aknoerig
Member
aknoerig commented Mar 7, 2016

We're still refining a few things while we're waiting for the final release of Qt 5.6 (which brings High-DPI support). It's scheduled for sometime in March, expect our release shortly after.

@mearsy
mearsy commented Mar 30, 2016

Now qt 5.6 is out any idea when fritzing 0.93 will be released. im kind of stuck until i can fix my bendpoint issue

@aknoerig
Member
aknoerig commented Apr 3, 2016

Getting really close now.. Note that Fab is already using it, so pcb orders will be fine.
Which OS are you on? Maybe we can issue a pre-release.

@mearsy
mearsy commented Apr 4, 2016

Osx

On Sunday, 3 April 2016, André Knörig notifications@github.com wrote:

Getting really close now.. Note that Fab is already using it, so pcb
orders will be fine.
Which OS are you on? Maybe we can issue a pre-release.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3115 (comment)

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