Closed GoogleCodeExporter closed 8 years ago
I added the wxProgressDialog code to the RS274X import routines because they
take so
long. It almost doubled the time taken to process the data. I ended up
removing it.
While looking for the class name to describe this, I came across the wxBusyInfo
class. Perhaps we should try that one too.
I just wanted to add that, if someone does add this sort of functionality, can
they
compare how long it adds to the overall process. My experience was that it
wasn't
worth the extra time. If it's insignificant with respect to the original
function's
processing then I agree that it's a good idea.
Original comment by David.Ni...@gmail.com
on 10 Jan 2010 at 11:46
The wxBusyInfo class seems to be quick for Windows at least. I will probably
checkin
the use of this class in the RS274X code. I will check to see if it's also
fast on
Linux when I get home. If it is, this might still be a good option for the
execution
of both the generation of GCode (python scripts) and the re-reading of the
generated
GCode. This would not offer any better granularity than telling the operator
which
python script is being run but it would be better than nothing.
Original comment by David.Ni...@gmail.com
on 11 Jan 2010 at 2:51
[deleted comment]
Unless someone else has better luck, the wxBusyInfo class doesn't work very
well on
Linux. It displays a square but I can't see the text within it. It works
alright on
Windows. Perhaps there is another option.
Original comment by David.Ni...@gmail.com
on 11 Jan 2010 at 11:34
For operations on a surface, look at the "Print" window, there will be some
indication of progress there.
Original comment by danhe...@gmail.com
on 24 Mar 2014 at 4:53
Original issue reported on code.google.com by
jbra...@mts.net
on 10 Jan 2010 at 9:31