topic How to constrain dynamic hotspots to set distance intervals? in GDL

How to constrain dynamic hotspots to set distance intervals?

Mats_Knutsson — Tue, 23 Nov 2021 21:22:23 GMT

I'm creating an L support that have length from 1 to 2 m in increments on 0.1 m. I vaguely remember a list or array in the parameter script but I can't find the example I did (got helped by someone here) a long time ago. Anyone with a fresh mind?

Re: How to constrain dynamic hotspots to set distance intervals?

DGSketcher — Tue, 23 Nov 2021 21:28:46 GMT

@Mats_Knutsson Try adding this into your Parameter Script...

VALUES "My_Parameter" RANGE [ 1.0, 2.0 ] STEP 0.1

Re: How to constrain dynamic hotspots to set distance intervals?

DGSketcher — Tue, 23 Nov 2021 21:39:21 GMT

Checked syntax... try this instead

VALUES "My_Parameter" RANGE ( , 2.0] STEP 1.0, 0.1

Re: How to constrain dynamic hotspots to set distance intervals?

Barry Kelly — Wed, 24 Nov 2021 01:38:55 GMT

You can also do it without the RANGE - although that is probably the better way to do it.

VALUES "My_Parameter" 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 2.0

Barry.

Re: How to constrain dynamic hotspots to set distance intervals?

DGSketcher — Wed, 24 Nov 2021 09:06:56 GMT

And to take @Barry Kelly solution to it's inevitable conclusion...

Create an array containing the value list ( DIM ValList [11] ) above and then simply use...

VALUES "My_Parameter" ValList

Re: How to constrain dynamic hotspots to set distance intervals?

Mats_Knutsson — Thu, 25 Nov 2021 06:46:21 GMT

Thanks again! Actual code snippets like this is king! I wonder why GS doesn't produce a bunch...? They describe the gdl in a very technical way in the manual. I'm not a programmer at all...barely survived the mandatory pascal at school back in 1989...but I can understand pretty much when I see the coding in a real example. I mean, look at the prism command... try to do a filled circle from reading the manual...hmmm...

Now I'll create a few tree symbols. Our landscapers (20 odd people) are going to change from Autocad+NovaPoint to Archicad+Land4 and they need some simple library parts to get going. Funny project :). We'll save huge amounts of money bu changing software and as icing on the cake we get better functionality.