Closed GoogleCodeExporter closed 9 years ago
Oh and secondary to the issue: How do I repair the file without losing my wires?
Original comment by martin.e...@gmail.com
on 17 Aug 2010 at 4:23
Hi Martin,
Actually, even though some of those wires are not visible, they carry
information that the application uses, and it's not safe to delete them. Is
the repair.fz file attached from before you hand-edited the file or after? It
would help us most to have the "before" file.
Thanks.
Original comment by irasc...@gmail.com
on 17 Aug 2010 at 6:28
I have edited it once, but it started happening again, without adding more
"visible" wires. I can attach the old version from before I edited it the first
time.
Original comment by martin.e...@gmail.com
on 17 Aug 2010 at 6:35
Attachments:
Hi Martin,
Just to let you know I can confirm crashes after autorouting. Don't yet have
an idea what the problem is, or even a regularly reproducible way to get it to
crash. So far the crashes occur at save time, not at reload time.
There was some trouble with JumperItems in 0.4.0 and 0.4.1. Did you happen to
notice whether the the crashes only started happening after the autorouter
started adding JumperItems to the sketch?
Original comment by irasc...@gmail.com
on 17 Aug 2010 at 8:40
It might have. It didn't start happening until I started doing the PCB, so I
suppose that is possible.
Original comment by martin.e...@gmail.com
on 17 Aug 2010 at 8:49
Just an update. (I have a deadline on another project, so I haven't had much
time for looking into this issue.)
My suspicions are still on jumper items. I'm now regularly able to crash
0.4.2b by loading the file from comment 3, autorouting (in PCB view),
selecting a jumper item (the biggest one seems to be in front, so it's easy to
select) then simply moving it using arrow keys.
Interestingly, although the current working build of 0.4.3b is otherwise
unstable, I have not been able to get it to crash after multiple autoroutings
of the same file, or following the recipe above This makes me less inclined to
delve too deeply into the problem.
I guess the way forward would be to checkout fritzing source from the time of
the 0.4.2 release, and run that in the debugger, hoping that the crash makes
itself clear. I'm not sure how soon I can get to it--maybe some time over the
weekend, if I'm ahead with the deadline.
In terms of workarounds, you might consider deleting the jumper items and
replacing them with vias--this is just something to try, I can't guarantee the
outcome. I will say again that hand-deleting wires from the xml file is very
unsafe
Original comment by irasc...@gmail.com
on 19 Aug 2010 at 7:37
I can't even delete them without crashing.
But I'll just wait for 0.4.3b then, I'm not in any hurry to finish this project
anyway. :-)
Original comment by martin.e...@gmail.com
on 19 Aug 2010 at 7:43
Took a quick look in the debugger, and the problem seemed to be with the jumper
wire rather than the jumper items--at least, with that wire removed, the crash
described in comment 6 no longer occurs. So I've attached the version of the
file from comment 3 with the jumper wire removed. Let me know if that helps.
My suggestion for now would be that you delete jumper wires (as opposed to
jumper items).
Original comment by irasc...@gmail.com
on 19 Aug 2010 at 8:42
Attachments:
Thanks :-)
Original comment by martin.e...@gmail.com
on 19 Aug 2010 at 8:57
0.4.3. I can no longer replicate the crash bug (with or without jumpers), but
there is a new strange behavior to report--possibly new since Qt 4.7? In PCB
view, select a jumper item, and move it a few times using the up-arrow key. If
you try to select anything else in PCB view thereafter, you are unable to. You
can switch to another view, and when you return to PCB view, you still can't
select anything. If you move the jumper using the up-arrow key another 10
times or so and then try selecting other items, then it works.
Original comment by irasc...@gmail.com
on 27 Sep 2010 at 11:25
Original comment by irasc...@gmail.com
on 27 Sep 2010 at 11:25
Jumper wires are gone. Closing. Moving comment 10 to a new issue.
Original comment by irasc...@gmail.com
on 29 Sep 2010 at 6:37
Sorry... I am still able to reproduce this in 0.4.3 with this file...
Original comment by martin.e...@gmail.com
on 5 Oct 2010 at 2:43
Attachments:
Hi Martin, could you upload the file again--the one in comment 13 shows zero
bytes long.
Original comment by irasc...@gmail.com
on 5 Oct 2010 at 3:35
Original comment by irasc...@gmail.com
on 5 Oct 2010 at 3:35
Yeah, apparrently, fritzing does that to the file, if you save it while that
has happened to it.
I'll restore a backup from my time capsule when I get back home.
Original comment by martin.e...@gmail.com
on 5 Oct 2010 at 5:00
I went back to the file attached to the original bug report from August 17th.
If I open that file, switch into pcbview, delete all traces, and try to save,
Fritzing crashes during saving. Happens every time.
If you open that file in fritzing, there's a strange thin wire that dangles at
the bottom right of the breadboard, and the "same" wire is visible on the upper
right side in pcb view away from everything else. I don't know how that wire
came to be in those two places, because it shouldn't be there--it's actually a
schematic wire that only belongs in schematic view--I don't know how it climbed
over the fence. So when I edited it out of the breadboard and pcb view, no
more crashes.
I've attached the edited version of the file, after a couple of rounds of
autorouting. Let me know if you still have troubles.
Original comment by irasc...@gmail.com
on 5 Oct 2010 at 11:47
Attachments:
Original comment by irasc...@gmail.com
on 2 Jul 2011 at 8:41
Issue has moved to new issue tracker at github. Please continue the discussion
at https://github.com/fritzing/fritzing-app/issues
Original comment by andre.knoerig@gmail.com
on 23 Sep 2014 at 3:37
Original issue reported on code.google.com by
martin.e...@gmail.com
on 17 Aug 2010 at 4:05Attachments: