generative modeling for Rhino
Preview is the same you get for all components. It either hides or shows data inside the inputs and output parameters. Preview content also previews geometry that's only inside the cluster.
Thanks David, I understand.
If i have compoment with preview ON in cluster, when I desactivate preview contenst, the compoment preview OFF.
For the flip an curve, have you got a report of bug ?
Thanks David !
Could you grant my [I wish that we could access to the input of parameter values by double-clicking on the parameters instead of Right click + "Set...".] wish ?
I noticed this today:
-Params > Input > Gradient: Unless you double click on a dot defining a color, you cannot edit the color from the Gradient component editor. Selecting a color dot does not stick.
Also, in the tooltips, I liked to see the data type when hovering over an input or output. Now we have just the icon of the data type, which says the same, but I liked reading the data type as well. Anyways, this one I can live with and adapt ;)
Many thanks for this update. I note that you have now incorporated the password protected cluster feature. This is really useful.
Is anyone else having trouble running Python in the version of GH? Rhino is crashing when I try to open the editor.
Isn't autosave now supposed to save files even if they haven't been saved yet? I just had a crash on an "unnamed" document, reopened grasshopper, and pulled up the autosave directory to find it empty.
It's not. You have to save the file at least once before AutoSave kicks in.
well then consider this a request for GH to autosave unsaved files, the same way Rhino does. It sounds stupid (who makes a big definition without saving even once?) but I've definitely lost work this way in this and prior versions.
There's a problem I haven't been able to solve with this. What if you start a second Grasshopper while you have these 'unsaved-autosave' files? How can Grasshopper #2 figure out whether these files belong to an already running Grasshopper and should therefore be ignored or whether they merit displaying a recovery window for?
Of course the same problem exists with regular files. If you open a second Grasshopper and open a file which has already been opened, you also get a recovery window. Not ideal all round...
I'm sure there's a way to solve it, just haven't figured out a good way of doing it.
Maybe : There are 3-5 "free autosave" files, where non of these files is associated with particular file. Each autosave operation is performed on earliest file, when file is saved, its autosave derives name from it (like it is now).
And cause now autosave performs quite often (i set it to each major change in def), these autosave "slots" would perform each 5-15 mins.