PR #868: History storage framework and options for select methods in TopoShapePy

Post here if you have re-based and finalised code to integrate into master, which was discussed, agreed to and tested in other forums. You can also submit your PR directly on github.
Post Reply
jnxd
Posts: 162
Joined: Mon Mar 30, 2015 2:30 pm

PR #868: History storage framework and options for select methods in TopoShapePy

Post by jnxd » Sun Jul 09, 2017 6:54 pm

Link to PR

Supported methods (all booleans, extrude, mirror, makeFillet2, makeChamfer2) now come with an optional withHistory parameter that can be set to True if you want to store history. The development of the sub-shapes from the sub-shapes of the base(s) can be studied by using shapeName.History.modified, shapeName.History.generated, shapeName.History.isDeleted.

Some testing is required, however. Works well enough for my test cases, but they are fairly naive. Some stress-testing would be greatly appreciated.

ezzieyguywuf
Posts: 635
Joined: Tue May 19, 2015 1:11 am

Re: PR #868: History storage framework and options for select methods in TopoShapePy

Post by ezzieyguywuf » Thu Nov 23, 2017 1:07 am

Bump: is there a reason this has not moved forward?

Post Reply