after autorouting there is a very long delay until the sketch is responsive to mouse input

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing

0 stars 0 forks source link

after autorouting there is a very long delay until the sketch is responsive to mouse input #893

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The delay begins after the autorouting progress dialog disappears.  is this 
only on my pc, or is it a general problem?

Original issue reported on code.google.com by irasc...@gmail.com on 29 Oct 2009 at 2:53

GoogleCodeExporter commented 9 years ago

Yes, I can confirm this here. No clue why, though.

Original comment by andre.knoerig@gmail.com on 29 Oct 2009 at 5:50

GoogleCodeExporter commented 9 years ago

not seeing this one on the mac

Original comment by irasc...@gmail.com on 24 Nov 2009 at 4:34

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 28 Sep 2010 at 5:07

Added labels: Component-Autorouter

GoogleCodeExporter commented 9 years ago

I think this has to do with all the clean up and undo stack processing that 
takes place when autorouting finishes--this can be a huge amount of stuff.

Original comment by irasc...@gmail.com on 2 Feb 2011 at 11:40

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

There is another case: Deleting all traces on a board also takes a long time 
and there is no feedback.
Can we get a modal progress bar for these things? That would be nice.

Original comment by andre.knoerig@gmail.com on 26 Sep 2012 at 1:33

Added labels: Priority-Medium
Removed labels: Priority-Low

GoogleCodeExporter commented 9 years ago

It also takes a large amount of time to select components using Ctrl-A. The 
time is much larger than just selecting all the parts using the mouse.

Also, after selecting many components, unselecting one of them (by Ctrl-click) 
takes a lot of time (this operation is useful when moving a set of components, 
because the PCB gets always selected so it needs to be unselected before the 
move).

Original comment by jerome.b...@gmail.com on 27 Sep 2012 at 8:20

GoogleCodeExporter commented 9 years ago

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

Changed state: ToGithub