Extract tool data from gcode comments

[rsteckler]

Feature Request

Parse tool information directly from gcode comments instead of requiring manual tool library setup.

Use Case

Many post-processors (especially custom ones) include rich tool information in gcode comments that could be automatically parsed to populate tool data during job setup.

Example: Vectric Post-Processor Output

Benefits

• Eliminates need to manually define tools that are already in gcode
• Leverages existing CAM workflow without changes
• Provides better tool change prompts ("Next tool is Carbide 201, 1/4" square")
• Enables automatic tool usage tracking with proper names/descriptions

User Feedback

"Looking at your gcode, I think it's probably better to just pull the tool data out of the comments! I'll add that to the list."

"Some of the info in the quotes shows up in the message box in CM. It has better tool change info than what CC feeds to CM."

"CC doesn't have those comments so I wouldn't remove the capability you have in have in their now. Maybe add the extraction from the gcode comments if it's there."

Implementation Notes

• Should complement, not replace, manual tool library
• Parse common post-processor comment formats
• Fall back to manual tool library for missing data
• Allow user to save parsed tools to library for future use

Priority

Medium - Automation feature that improves workflow efficiency and tool tracking accuracy.