You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would help a lot if the "refactored" postprocessors could be configured to replace the command strings ("G01", for example) and/or the parameter strings ("Q", for example) with user-specified strings without having to modify the code that is shared between all of the "refactored" postprocessors.
A specific example would be replacing "Q" with "I" in the drilling G-code commands (G73 and G78).
In the non-refactored postprocessors a few lines of code need to be changed to do this, but in the "refactored" postprocessors there isn't an easy place to make a similar change without affecting all of the "refactored" postprocessors.
Anything else?
I intend to figure out a way to do this to the "refactored" postprocessors eventually, but don't want the idea to be forgotten.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
luzpaz
changed the title
Path: Be able to replace command or parameter strings in the "refactored" postprocesors
[Feature Request] CAM: ability to replace command or parameter strings in the "refactored" postprocesors
Mar 13, 2024
Is there an existing request for this?
Forums discussion
https://forum.freecadweb.org/viewtopic.php?f=15&t=73915
Subproject(s) affected?
Path
Idea description
It would help a lot if the "refactored" postprocessors could be configured to replace the command strings ("G01", for example) and/or the parameter strings ("Q", for example) with user-specified strings without having to modify the code that is shared between all of the "refactored" postprocessors.
A specific example would be replacing "Q" with "I" in the drilling G-code commands (G73 and G78).
In the non-refactored postprocessors a few lines of code need to be changed to do this, but in the "refactored" postprocessors there isn't an easy place to make a similar change without affecting all of the "refactored" postprocessors.
Anything else?
I intend to figure out a way to do this to the "refactored" postprocessors eventually, but don't want the idea to be forgotten.
Code of Conduct
The text was updated successfully, but these errors were encountered: