Error with sliders and expression

I am currently running rhino 5, under 64 bit OS.

and I have been trying to run a def for 2 days with no luck.

I thought the def was way to old to work on the current version of grasshopper but until I ask for some help and I sent the def to someone who tested the def out and made it work and send it right back to me and I got the same error I realized something wasnt right.

here some images of what the def does

Flat hexagonal panels over a given surface.

I get errors with the sliders and the VB script. Original script by Luis Fraguada from LAN then Davide del Giudice/ from madeincalifornia Checked out the definition because I have almost no knowledge with scripting and he made it work and sent those images back to me and this definition fixed, wich doesnt work on my computer and here some images of the problem.

and here some images of the problem.

Attachments:

xx_Hexagonal planar with span_Co-de-iT.gh, 21 KB
Planar HEXAGONAL SURFACE.3dm, 95 KB

Replies to This Discussion

Permalink Reply by Andrew Heumann on March 11, 2013 at 9:02pm

Try this version - I've rewritten the original script in RhinoCommon and put it in a non-legacy VB.NET component.

Attachments:

xx_Hexagonalplanarwithspan_CodeiT.gh, 28 KB

Permalink Reply by Francisco Lara on March 11, 2013 at 9:09pm

Amazing!

You did it man!

So it was definetly the VB script bug or problem!

What is a legacy VB.NET component....I dont really know much about scripting it gets too complicated for my small brain XD

Thanks Andrew Heumann for fixing this for everyone!

Permalink Reply by Michael Pryor on March 11, 2013 at 9:17pm

Interesting andrew, when I put an expression in the slider say x*2 with the value set to 2 I still get 2 as the result. Also, rhino 5 64 bit.

Permalink Reply by Francisco Lara on March 13, 2013 at 8:32pm

I ran into an other situation where there is a VB.NET component.

I am guessing is the same problem from before. something that as to do with the scripting.

did you just copied and pasted the same text into a grasshopper non-legacy VB.NET component or you had to change some things?

thanks again

Permalink Reply by Francisco Lara on March 13, 2013 at 8:37pm

wow I just realized what you did for me!

Link

Thanks again!

I got it now!

Permalink Reply by Francisco Lara on April 26, 2013 at 9:23am

Andrew Heumann

You are the only person I know that could help me out with this

http://www.au-urbanfuture.org/blog/?p=809

I have the same problem with adapting the definition to the new version of script.

please help me out!

Thank you in advance. I appreciate it!

Permalink Reply by Francisco Lara on March 11, 2013 at 8:37pm

Here I fixed both sliders changing the expression but the script comes out NULL ANYWAYS!

WHY?

Permalink Reply by Luis Fraguada on March 12, 2013 at 2:32am

Just for the record, I opened this definition, referenced a Surface, and it worked fine. I did not modify the sliders, they gave errors, but still passed the number. All I did was open and reference the surface. I am not saying that it is correct, the def should be rewritten, but besides some red sliders and slow operation, it works as it did in v 0.6.xxx

Rhino 5 x64, GH 0.9.0014 for Rhino 5, Windows 7 .........