[Bug?] "Read File" component doesn't work on Mac

Hi

I let Read File component read a txt file. It stops working on Mac, but work well under Win.

Is it a bug?

Hi,

I don’t know, if the bug still persists or if it has already been fixed in a newer version, but it’s been reported a couple of times in the last half year or so:

I’ve posted a work around or alternative using GHPYthon here, if you’re interested:

I usually don’t use the File (ā€œRead Fileā€) component, since I oftentimes need more specific text parsing or type casting workflows.

It could simply be that Rhino has not the right privileges (i.e. Full Disk Access) to read the file at the given location?

1 Like

your script works on Mac. Thank you!

Yes, I’m also a macOS user. :wink:

1 Like

@dan, I don’t know if your the right person to ask, but why hasn’t this been fixed yet? It’s been over half a year since it was first reported. Respectfully, it doesn’t seem that hard to do, if I can whip up an alternative with a few lines of Python.

Screenshot 2021-08-12 at 07.57.18

1 Like

Hi @diff-arch If I’m not mistaken, it is this bug:

RH-36840 File Reader component errors

which was reported here and we did indeed fix it.…but, as sometimes happens, it got ā€œunfixedā€ (aka: a regression). I’m going to check in and see what happened here and report back. Sorry about this.

2 Likes

Thanks @dan! Seems to be a hard piece of code to keep running. :slight_smile:

I’ll say! I haven’t looked at source on this - I’ll go do that soon - but I think this is one where it’s very old VB.NET code getting run in Mono on macOS. I don’t know how many users this impacts just yet (we’ll take a look soon), but this might warrant a hot-fix update.

Regardless, this is an :egg: meets :face_with_monocle: regression.

Tracking the same problem here:

Seems to be an issue with VB (getting a VBNC_CRASH error in console that keeps the parser from compiling/loading).

See my answer there…
-w