Package Version 2.0.0
November 2019 - First Dynamo 2.0 Version Release - Bulk updates + 1 Node + 1 Depreciation
For this release, I focused on reformatting nodes for the new file formatting used in the latest Dynamo versions, and testing that they still perform as expected.
GENERAL NOTE: Nodes from all package sections have been upgraded.
(Sastrugi_Annotations)
❄_Levenshtein String Comparison
This node compares the minimal number of deletions, insertions, or substitutions that are required to transform strings from a source list into a target string and outputs the best solution.
(Sastrugi_Management)
❄_Audit DYN File (DEPRECIATED)
DEPRECIATED NOTE: The development of functionality to identify nodes and their dependencies within graphs has been a hot topic on the forum, and with the Dynamo team. Extensions such as Monocle by John Pierson perform the feature this node demonstrated very well, and the newer releases of Dynamo look to be including this functionality out of the box.
(Sastrugi_Pointcloud_Geometry)
❄_Pointcloud Select Points in View (Renamed from ❄_Select PointCloud Points in View) (UPDATES INCLUDED)
UPDATE NOTE: The updates to this node mentioned in the 0.1.5 release documentation have been incorporated within this release. The Downloads link will remain active for anyone requiring a Dynamo 1.3 version.
2019-11-08 UPDATE NOTE: I have revised the node to allow for better stability of point selection in 3D views, plan views, section views and detail views. I have also removed the need for the box selection corner order, so users can now create a selection box from any corner, in any direction. Also, I identified that there is a disconnect between the Active View plane refresh in 3D views that may cause the node to return a Null value. When a user rotates around the Pointcloud in 3D after starting the selection process with the node, the original view perspective normal is used to generate a selection box, not the perspective the user might end up drawing a region in. This is a workflow issue, so I have included a "Troubleshooting" help message as a node "input" to alert users of this and what the workaround will be. Download from here.