I have the need for a python accessible configuration file - which, potentially, could become rather big. I would like it to be a human read-edit-able format (and xml doesn't fall into that category in my book). The config file needs to support multiple instances of the same object (array, list, tab...

It seems ppl still use PathArray, so maybe we keep that for now until we find something better. I question the value of keeping the other ones around - given that they've been broken for quite some time and nobody seems to have noticed, or cared enough to point it out....

my 2C

Cool - thanks for the clarifications. I'm going in

I personally would like to have the option where output filename automatically follows document name. So if I'm working on mybigpart.fcstd, the default output file would be mybigpart.ngc You can set that up in the preferences (check the tooltips for a complete description). I'm in the same boat and...

... Instead it should create edges only after it is 100% sure about the actual position. ..... I got it to work with my very limited test case. But the solution smells lika a disgusting hack to me. :D Any better ideas? Would it be possible to compare with the original starting/entry commands? Depen...

I would like to remove all currently unused properties in PathJob. Specifically X/Y/Z_Max/Min MachineName MachineUnits There are 2 properties I didn't name properly: DefaultOutputFile -> PostProcessorOutputFile DefaultOutputPolicy -> PostProcessorOutputPolicy And finally there is the corresponding P...

Finally had some time to look at the new code and figure out what happened in the past months. Specifically picking up where I left off and naturally everything is broken (it would be sad if it wasn't). So before I go "fixing" things some reality checks: Tooltable is gone from PathJob - that's perma...

I would hope that changing from two(2) digits to three(3) digits would involve nothing more than a few edits! And should not affect the tool table or its usage deleteriously. SpinBox in QT has a default min=0.0 max=99.0 setting - I assume that's all it is (and those defaults annoy the heck out of m...

When I add a HoldingTags Dressup to a profile the operation starts with a move to origin. .... If you have many pieces to profile this will of course add to the job time. Is there a purpose for this move or is it just a bug and the gcode line can be removed by hand? There's no specific purpose/reas...

sweet - I like it.

If one cares about surface finishing so much they'll probably add a helix to finish off at the end, so I wouldn't worry too much about it for this dressup.