If sucking on rocks is what you want - I am currently converting my grbl/bCNC machine to linuxcnc, give that a try.

jmr wrote: ↑

Mon Mar 25, 2019 9:41 pm

I agree this is somehow strange, as with other object or groups hiding the top thing is enough to make all content disappear.

Hiding is not the same as disabling - this is a constant source of confusion but as a group we have not found common ground on this matter.

I tried this: App.ActiveDocument.Job.Stock.Proxy.__init__(App.ActiveDocument.Job.Stock,App.ActiveDocument.Job.Model) I am not sure what you are trying to do here. You should never call __init__ manually, or execute for that reason. All you have to do is assign the Stock object in your job: job.Stoc...

My thinking is that maybe I can just hijack some of the code out of linuxcnc_post.py and get it working in the grbl post processors. Anyone that has written a post processor think that would work??? I haven't written the linuxcnc post processor, but I added the --inches option to the opensbp post p...

I haven't done any experiments in real 3D yet (have enough problems with 2.5D)

Of all the attempts and test cases for 3d milling with Path I love this one the most. It is so simple I would've thought 3D Surface would be able to create a good Path for sure.

All "Refresh" does is create a new Stock object and assign it to the job. You can do the same in your script. If you look int PathStock.py you'll find creation functions for all stock types towards the bottom.

awesome - thanks for reporting back!

Sounds like a bug to me - could you file a bug report?

No intention - I think it's just that nobody's needed it so far.

I would very much like to see this and function this way. Path is starting to have similar problems and we probably want to decouple Path generation from the automatic recompute/update mechanism soon - as we get into 3d machining and support for complex models. Probably not the strongest argument to...