Using ranges to define paths

Can't ranges be used to define paths ?

Wouldn't that be one of the obvious purposes of ranges ?

Replies to This Discussion

Permalink Reply by Joseph Oster on November 8, 2017 at 8:08am

define paths ?

Not sure what you mean? 'Consec (Consecutive Domains)' with 'Range' can be helpful:

Permalink Reply by David Rutten on November 8, 2017 at 8:12am

The Branch component only accepts Paths as input, and a path only allows for single integer numbers. The Split Tree component accepts text as input and this text can have various complicated meanings for each element in addition to just single numbers. See this post on what sort of stuff is allowed.

I agree it would have been nice if Tree Branch (and in fact all components dealing with paths one way or another) could understand more complicated notations, but all this functionality was developed over a long period of time and it wasn't very clear at all what would and wouldn't work. I hope to do better for GH2.

Permalink Reply by Olivier Suire on November 8, 2017 at 8:12am

OK, instead, I figured I should use the Path mask rules.

Since they are not in the "Split Tree" help box (for some reason), I used the help box from "Replace paths".

Sadly, I get an error message stating this :

Man ! This whole path management is stiff...

Permalink Reply by David Rutten on November 8, 2017 at 8:27am

Man ! This whole path management is stiff...

Yup... welcome to an organic development process where nobody really knows what they're doing.

These sort of inconsistencies are not just superficial in GH1, they go really deep into the core code. This is why I insisted on rewriting the next version from scratch rather than just twiddling with GH1.

Permalink Reply by Olivier Suire on November 8, 2017 at 8:38am

Well, I'm probably being a bit harsh since working on GH has managed to transform that boring job of mine into a captivating puzzle solving activity.

But now that I'm starting to get a clue about path management, I understand why it was so tough to get there.

In the present case, I'll try using series instead of ranges ; I guess that should do the trick.

RSS