Debbuging with 8.00000003

Hello,

When the script is not correct the out dont tell me the problem just "no data collected", so it's a bit difficult to debug the script.

This bug will be fixed in the next version?

thanks:)

p.s. see the attachement

Attachments:

Capture.PNG, 42 KB

Replies to This Discussion

Permalink Reply by Arend on December 9, 2010 at 1:43pm

You can hover over the little red box or right click the element and go to runtime errors to see the error.

I'm not sure if this is a bug: I can imagine since that the out variable also exists in the visual basic component that on certain errors the out also won't work, perhaps david can shed some light on that?

Permalink Reply by RG on December 10, 2010 at 3:31am

Hi,

Thanks to help.

The error on the runtime is verry strange, look the attach file

regards,

Renaud

Attachments:

runtime error.jpg, 120 KB

Permalink Reply by Giulio Piacentino on December 10, 2010 at 4:21am

Hi RG,

I've never seen this error before -- but it seems that the name of your windows user is "(in)visible", and it might be that open and closed parentheses influence how .Net resolves files.

Could you try making a new user account and use Grasshopper from there? Is it helping solving the issue?

Thanks,

- Giulio

____________

giulio@mcneel.com

McNeel Europe, Barcelona

RSS