Well, DXF import has been on my radar for years. This: Virtual Layout Feature Preview started as a DXF import, but then I ran into all sorts of problems and decided to dumb it down to just a bitmap import. In the bowels of the app there is also a full-fledged G-Code parser. The main reason this feature is not released is because I can't figure out how to make it work well. Bitmaps are too crude, and the workflow is pain ugly. G-Code is an overkill (and the same issue with ugly workflow). Basically DXF import is the right answer, but parsing DXF files is a LOT of work, and then I still can't figure out what to do with the file once I parse it.
Regards
Yuriy
@ycroosh you really have been reaching for interesting functionality! Thanks for sharing your thoughts and things that you have been working on.
The bitmap import would be a help since it could help address the data (entry etc.) verification that will come up with things like the project I had in mind. I have an instrument panel with numerous cutouts and fastener locations and the best way I have right now to verify the DRO data entry is printing a 1:1 and using it as an overlay. Being able to visualize the layout in TouchDRO would be a great feature!
I have more to learn about the .DXF format to understand how it would be useful. I'm theorizing about maybe putting different entities of the panel on different .DXF layers (overlayable datum work spaces?) so that the cutout lines wouldn't get confused with the coordinates of things like the corner points of the cutout (datum points that the milling cutter would use as vertices defining the cutout) and hole center (datum) points etc. You have probably thought this through already, I'll just have to be patient.
Thanks for sharing!
D