drilling order preempts milling

[GoogleCodeExporter]

I am milling a pocket that will later get holes drilled and tapped in the 
bottom. If I try to mill first and drill afterwards, the drilling operation is 
output to python before milling. For some reason the operation tree is ignoring 
the order of operations.

Original issue reported on code.google.com by ddfalck2...@yahoo.com on 28 May 2011 at 6:07

[GoogleCodeExporter]

Dan,

If you look in Program.cpp, you can see that I removed the sort_operations line 
from the Windows build, like this:

#ifndef STABLE_OPS_ONLY
    // Sort the operations in order of execution_order and then by tool_number
    std::sort( operations.begin(), operations.end(), sort_operations() );
#endif

You could define STABLE_OPS_ONLY for the Linux build, to get the same as me. I 
am reluctant to simply remove the line, as David may still want it?

Original comment by danhe...@gmail.com on 28 May 2011 at 10:51

[GoogleCodeExporter]

You can go ahead and remove it.  The sorting process used to use the 'execution 
order' integer as a first sort key.  With that gone, it just contradicts the 
idea of allowing the operator to manually arrange the order.  It makes sense to 
remove it.

Original comment by David.Ni...@gmail.com on 28 May 2011 at 10:55

[GoogleCodeExporter]

OK. I removed it completely. Thanks Davd.

Original comment by danhe...@gmail.com on 28 May 2011 at 11:04

• Changed state: Fixed

[GoogleCodeExporter]

Thanks!

Original comment by ddfalck2...@yahoo.com on 29 May 2011 at 1:50