Forum Guides after Dynamo 2.0


#1

Hi all,

I’ve just saw this answer where a solution is given using Dynamo 2.0 but users are implementing it in 1.x and therefore it didn’t work.

I see that on the future, due to the considerable changes on the Dynamo API from 1.x to 2.x most of the current solutions on the forum will not be aplicable, and people unfamiliar with the forum will fail to apply a solution for 1.x on newer version.

Can I suggest to add a tag identifying topics/solutions as pre-2.0 / post-2.0 or something similar? (not sure how discourse works). Also, it would be good to remind somewhere on the guides that as “good practice” topics/answers need to specify the version they relate to.

@Michael_Kirschner2 @Racel_Williams @Zach_Kron


#2

The major problem is actually quite easy…

Lists is in Dynamo 1.3.x is set with curly brackets -> { }
Lists is in Dynamo 2.0 is set with square brackets -> [ ]

In most cases is curly brackets replaced with square brackets when opened in dynamo 2.0 automatically. BUT in custom nodes, if the default input is set in the input node using lists, then there isn’t any brackets being replaced!

This is potentially a huge problem if many who build custom nodes are using default input and not are aware of this fundamental change. This problem also affects default input in coding ZeroTouch nodes!


#3

@erfajo I understand your point and agree with you. I like to think that people doing any kind of development in Dynamo (custom nodes, zero touch, etc) are somehow experienced and aware of these changes and they will upgrade their nodes/packages accordingly.

My comment was focused more on the forum per se and people with basic knowledge or just starting with Dynamo, that on the event of looking for support on the forum they might try to apply a solution that works on 1.x but not on 2.x (like for example copy/paste a code block like on the example).

I am just thinking that by making this very clear on the forum guides and/or when posting will help on the future by avoiding “tried-this-but-not-working” type of comments in old posts when it is just a matter of different versions :slight_smile:


#4

Agree, but I think we will manage, just like when we moved from 0.6 to 0.7, and so forth… when we moved from 0.9 to 1.0 was there also larger changes. Back then, it became a habit to include the version number in the text for a while. I think this will be the same this time.


#5

Not a good idea, as topics could have responses that are a mix of both (and we can’t tag individual posts)

Good suggestion, but sometimes, one isn’t really conscious as to which version is being used to provide a solution. :slight_smile:

Besides, I suppose, mostly its solutions that incorporate some Design Script that would have a problem.


#6

Ok, thanks for the feedback :slight_smile: