import CSV

Hi,

I have used the code for importing CSV data from the following discussion:
http://groups.google.com/group/grasshopper3d/browse_thread/thread/8...

It worked perfectly until I installed a newer Grasshopper version (the one I had was pretty old). Is it possible that the new version needs different coding?

Any help is welcome!

Replies to This Discussion

Permalink Reply by David Rutten on May 24, 2009 at 6:13am

Hi Fizzgig,

could be, though it looks like that code should still work. Maybe there is a problem with DataTrees? Perhaps the data is stored in a way that is unexpected?

Is there an error message?

What does the output look like (please post a screenshot of the output as it is displayed by a TextPanel)

Permalink Reply by Farley2076 on May 27, 2009 at 1:02pm

FYI

I don't have the file to grab a screenshot, but I tried this last night and it didn't work for me either. The Runtime message said something about not liking or expecting or knowing how to "handle 'return' inside a Sub or Set' and that was with an actual .CSV file from Excel. When I tried in with a .txt file as you mentioned about there were no runtime errors, it just returned 'Null'

Permalink Reply by Simon Kallioinen on May 27, 2009 at 3:17pm

Hi Gelfling and Austin,

That is exactly the same problem. See screenshot for more info.

Thank you for your help!

Attachments:

dump.JPG, 116 KB

Permalink Reply by WT4 on May 27, 2009 at 4:30pm

Hi Fizzgig

Sub RunScript(ByVal path As String)
If (Not IO.File.Exists(path)) Then Return False

I found that if you simply remove the word False in the above line then it works.

WT4

Permalink Reply by Simon Kallioinen on May 31, 2009 at 2:31pm

Thanks a lot. It works. Weird that the same code worked in the older Grasshopper.

Permalink Reply by Damien Alomar on May 31, 2009 at 8:22pm

Did you by any chance ALWAYS have the file in the older version. The thing is that Subroutines can't return anything, but my hunch is that it will cause a runtime error instead of just "killing" the sub outright. Therefore, that line would only worry about "returning" anything (and thus cause the error) if the file didn't exist. Still odd though as I thought that error would get caught a little earlier (which apparently now it is).

Permalink Reply by Simon Kallioinen on June 1, 2009 at 11:56am

I can not remember exactly, but I would be very surprised (but it might be possible) if I always had a file when I used the older version. In the new version however, that doesn't matter, the error is there either way.

It is beyond my knowledge how it could work in the older version and not in the newer one, but the problem is solved, at least for me.

Permalink Reply by Matthew Kenney on March 7, 2013 at 8:58am