I find “DATA OUTPUT” and “DATA INTPUT” very promissing, but they don’t lend themselves to be used through a Human UI interface because the destination path and source path (respectively) need to be tweaked by right-clicking the component.
It’s even quite a source of error when you need to generate multiple GHDATA files.
It would be great that these paths be in fact an input of the components, but until this happens, perhaps Metahopper could address this ?
Best,
I could add these to metahopper if there’s interest… in the meantime here’s a script:
Set-data-input-output.gh (7.9 KB)
Thanks Andrew ! I’m going to try that out !
It doesn’t work here.
It might be related to a bug with data Output/Input that I noticed while on training with @DavidRutten in Barcelona whereby error messages are displayed in Rhino, but the ghdata files still get created.
Setting the same path through the component itself in the usual fashion works though.
It seems to me that these components are at the “Show-off toy” stage, but not ready to be used in a production environment, despite this being their real actual potential value.
Hey Andrew, I’ve been trying to solve this problem as well (control Data Ouput destination and Data Input source paths), however, I’m not that familiar with the c# environment, would you be kind enough to explain this to me? And, do you know if it is possible to do this in Python? Cause, I’m having a hard time trying to access IOComponents.
By the way, it would be awesome to add these to MetaHopper!
Hi Andrew
Thanks for the script. I am doing some testing with Data Input / Output + timer. And eventhough the timer is not connected to any Data Output, somehow the Data Output is writing the file each 10 seconds (regarldless of how much time I had set up in the timer). Do you know why this could be happening?
Would you be so nice to add this script as a component in your next Metahopper?
Regards
Luis de la Parra
Hey Andrew, this works brilliantly. Did you end up adding it to metahopper? That would be great, but I can’t seem to find it in the plugin
Hi Andrew,
I have been trying to update your component for it to work in R8.
I changed the Assembly to the R8 Assembly but it seems like the ‘DataInputComponent’ class got renamed/changed in R8.
The type or namespace name ‘DataInputComponent’ could not be found (are you missing a using directive or an assembly reference?) [46:9]
Does anyone know how this class is called in R8? Or if there is a workaround for this?
Thank you in advance!
Some namespace changed. Here are Rhino 8 compatible scripts, though unless you’re on Mac you’ll likely have to re-point them to the IOComponents gha, wherever it lives on your system (the line in the script where it says #r "/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Versions/A/Resources/ManagedPlugIns/GrasshopperPlugin.rhp/Components/IOComponents.gha")
Set-data-input-output.gh (8.9 KB)
