re:re:Re: gcode comments

Brian,

The camsoft program recently referred to in another thread does just this thing! Also many CAM systems.

It is quite a bit more "structural" work to write a cnc control program which allows this sort of functionality, but it can be done...

IMO, this is not the best way to approach this. We "should" try to coalesce (gather together) the g code usage, rather than make it easy to keep it different.

(more snips/inserts below)

>its the codes used to call those functions that we can't nail down

Sure we can. We just have to work together to do it!

>how about a config file to let the user pick the codes?
>sure the default values can be our version of the RIGHT codes ;-)

>but if the end user wants to change them to their preferred flavor
>(to match what they are used to) they should be able to without
>having to rewrite the whole package

Having "flavor packets" MAY make this economically feasible, since the extra work of setting up the program in this way (as shown in the CAMsoft price!) "could" be offset by the sale of these "flavor packets", mucch as posts (post processors) in CAM are sold now.

Hope this helps.

Ballendo