I've tested macro recording the other night, I created a PartDesign Body with 3 features (a pad, a pocket and a fillet). The odd thing is, it records every step, but it comments out the GUI operations. The result is, when you launch the macro to recreate the model, all three features are visible at the same time, when a Body should only show one at a time, the one defined as tip.
If I end up doing one or two macros, I'll need help to fix that, because I am clueless at Python.
kkremitzki wrote: ↑Sat Mar 02, 2019 7:26 pm
All the binary files have their types defined in the XML files, and the specifications for those types are as open and clear as the FreeCAD source code that defines them, so there's not really any mystery about a .FCStd file...
Come to think of it, it's the same thing for STEP, isn't it? Even more so, as STEP is just plain text. Does Debian consider it OK to distribute STEP files?
IMO we should still try to provide scripts for the example files, even if Debian is a very specific and marginal case in view of the FreeCAD users at large. Besides, it cannot hurt to show that those example files can be scripted, which might be useful for end users.
But I think not all example files are worthy of getting scripted, or even of being kept in binary format. I'm thinking of the EngineBlock which is 6-year old and no longer represents what FreeCAD can do. Just look at any miniature steam engine posted in the Users showcase! Then there's the DrawingExample, based on the outdated Drawing wb.
FreeCAD
