25 June 2019

Move an entire model and its views


Have you ever witness the challenge of working with a model that is started by someone who didn’t know the importance of controlling the project origin!?

As a university and an estate owner do we inherit many models made in projects where the scenario is that someone forgot to control this at an early stage so the model could have been corrected. First when the project comes to the handover phase is it then discovered that this very critical error occurs.

Therefore, I took this challenge to code the bits and pieces to be able to move an entire model including moving elevations, sections, detailing, and 3D views, etc., also including adjustments for grids, crop boxes, views location on sheets. All in all, everything inside the project should be transformed by a given vector.

This work made me walk along many paths, developing a variety of nodes for grouping, views, viewports, and grids. More than 25 nodes have been created.

However, In the final scenario, I ended up only using a few of these nodes, while I continuously tried to figure smarter and smarter ways to tweak data. The nodes developed along the way is released also, while these could be used for other purposes and/or minor other tasks than moving the entire project.


move to origin (the final graph)

---
nodes for spatial element (room, space, and area)

nodes for view, viewport etc.


nodes for grouping etc.

nodes for grids etc.





24 April 2019

Minor release 134.5.0 / 202.5.0 and major release 210.0.0


Revit 2020 (and Dynamo 2.1) has been released and therefore have I released my package for 2.1.x series. This has a huge impact on all version of the Orchid package since a large reshuffle of node locations has taken place.

Unfordenetly is the problems concerning migration not being solved with the Dynamo 2.1 release, however, it was not viable any longer to wait for a fix of the migration problem while it was slowing down my development.

This rather big issue will give users errors, and the only thing I can suggest is to address complains over this error towards the dynamo team at dynamobim.com forum and/or DynamoDS gitHub. I don’t find it suitable that I should correct this error, this must be an Autodesk issue.

26 March 2019

BuiltInParameter, Transfer/Copy, central/linked files

In this update have I added several new features in different areas.

Nodes for BuiltInParameter

Nodes for copying and transferring elements between different document

Nodes for opening, save and closing central files

Nodes for linking files into documents

15 March 2019

Graphs...

I have seen it over and over again. Users calling Dynamo "graphs" as "scripts". Sorry but this is not what it is!

What we do with Dynamo is much smarter, it is directed graph technology. It is a much higher order way to do (visual) programming, than simple scripts known from ex. Java scripts, or even the way Python scripts is widely used in Custom Nodes... or scripts in Code Blocks.

Naming it "scripts" is to patronize what we actually do.

https://en.wikipedia.org/wiki/Directed_graph
https://en.wikipedia.org/wiki/Visual_programming_language
https://en.wikipedia.org/wiki/Graph_rewriting


Try also to open a dynamo 1.3 file in a text editor...
<Connectors>
  <Dynamo.Graph.Connectors.ConnectorModel ... />
</Connectors>


Or take a look at the Dynamo Primer...


...and from https://primer.dynamobim.org/13_Best-Practice/13-2_Graph-Strategies.html

Reduce Complexity
As you develop your Dynamo graph and test ideas, it can quickly grow in size and complexity. While it is important that you create a functioning program, it is equally important to do it as simply as possible. Not only will your graph run faster and more predictably, you along with other users will understand its logic later on. The following are several ways that will help you clarify the logic of your graph.

[...]


Maintain Readability

In addition to making your graph as simple and efficient as possible, strive for graphic clarity. Despite your best efforts to make your graph intuitive with logical groupings, relationships might not be readily apparent. A simple Note inside of a Group or renaming a slider can save you or another user from unnecessary confusion or panning across the graph. The following are several ways that will help you apply graphic consistency within and across your graphs.


It does matter to use a "language" thoroughly. Giving up language is giving up the core of whatever a culture stands for. Therefore, I don’t think it is a good idea to let "slang" become the language!

Please let us use the right notation... it is graphs, not scripts!

10 March 2019

New nodes for materials

The update x.4.1 includes a new branch for “Materials” and +100 new nodes handling generic material-, graphical-, appearance-, physical-, and thermal assets.

Material general


Graphics


Physical and Thermal


Appearance

25 February 2019

IFC export and some other new nodes

The major update release (134.4.0 and 202.4.0) includes nodes for IFX export.
The nodes is build using the API from the IFC exporter 18.4.0 (for dynamo 1.3.x) and 19.1.0 (for dynamo 2.0.x), meaning the exporter must be installed to use these nodes!



Building the exporter nodes made me realize that some project nodes also was needed


Dropdown for families in the project and selection of all elements by family in the document added.


String.Substring and String.Replace added, these takes lists as input!
can be used for "manually" migration of dynamo files
https://forum.dynamobim.com/t/dynamocore/31912/13
https://forum.dynamobim.com/t/migrate-custom-nodes-to-zero-touch-nodes/31585/8



09 February 2019

Open new view ... active view

I have made a node for opening a new view, this new view will then be the active view when the graph is finished and the dynamo application again is idle. However, this is only one half of what I would like to be able to do with my node. My goal was to be able to close the other open windows in the same process.

That is not possible at the moment due to the way Dynamo works. If it should be possible I need the ability to use events inside a method in Dynamo like this post by Jeremy Tammik describes.

Therefore, is the workaround at the moment as following. Add the “OpenView” node in a graph and then execute the graph and do whatever is needed. When you eventually has finished doing whatever you should, then save and closes the file.

When the file is re-open will the last view be the default view unless starting view is set, in that case, will it be the starting view and that would be correct in those cases.

This new node cannot be called as a background action!