So why would you want this? Sooner or later there is going to be some geometry Fusion can't handle; the solution sometimes is to just hand code these situations. This feature would allow the user to either import some gcode from a file -or- copy and paste it into an edit box. In addition to all the machining strategies offered, there could be one that says 'import', 'raw code', or something to that effect. The setup would contain four tabs:
1) the Tool tab, for speeds, feeds, coolant, normal tool info.
2) Geometry tab, which would carry 'Z" information and extents, but could be left empty.
3) Radius ( for lathe ops ), again could be left empty.
4) GCode - with a file selector and/or edit box.
Benefit:
This gives a solution for 'all' the arcane geometries that are difficult to create toolpaths for. It allows the user to go back and iterate design/machining strategy, without messing with work flow to copy and paste in segments in the gcode after post processing.
Extras:
Once the gcode is place, it could be parsed and a toolpath generated like any other op .. and possibly simulated.
Use-case:
I customer needed some parts for an aircraft engine that had a forward facing 45degree face with a dovetail o-ring groove in it. This was cut with two grooving tools that sat at 45 degrees to X,Z. One cut one side of the groove, the other the other. Both had to be hand coded, about 30 lines each. It would have been awesome to have a feature like this.