internal input data gets lost when re-opening files

Hey all,

I am having this problem for quite a while now, which persists with the latest release (0.9.70.0):

gh "forgets" the internalized data that i have in input hooks (for example i had a subtraction component with 1 in the B hook, and it got lost). I have to use panels to make it remember, which is quite annoying.

Does anyone have a solution to this? Thank yous!

Replies to This Discussion

Permalink Reply by David Rutten on February 25, 2014 at 10:42am

Hi Andrei,

is this repeatable? Does the data disappear every time?

David Rutten

david@mcneel.com

Permalink Reply by Andrei Raducanu on February 25, 2014 at 11:14am

Hi, David,

Seems so... i just unloaded gh and opened it again and it did lose it

Permalink Reply by patric guenther on February 26, 2014 at 10:24am

same problem here since a while

Permalink Reply by David Rutten on February 27, 2014 at 12:30pm

Ok please upload the file that doesn't open correctly. I need to figure out whether the problem is with the writing of the data or the reading of the data.

David Rutten

david@mcneel.com

Permalink Reply by Andrei Raducanu on February 27, 2014 at 12:41pm

here you go (input B should have 2 as internal value)

Attachments:

amnesia.gh, 3 KB

Permalink Reply by David Rutten on February 27, 2014 at 1:55pm

Yup. The data is there but is clearly not getting read correctly. With a bit of luck I can fix this bug tomorrow.

Thanks for posting it, this was starting to get very serious.

David Rutten

david@mcneel.com

Permalink Reply by Ryan Hoover on March 3, 2014 at 2:16pm

Thanks for looking into this, David.

I've had the same problem. Thus far for me, the problem seems to be with math operators.

I look forward to the fix.

Thanks!

Ryan

Permalink Reply by lmnts on February 27, 2014 at 2:11pm

We've been experiencing this same issue so it's great to hear that a fix is potentially on the way. One of the difficulties that this brought up was finding the component within the definition that had lost the value.

It seems like it could be useful to have an option for highlighting all components that contain Null values. I imagine this might work similar to the canvas Find option. In this case there would be a canvas Null option which would draw a circle around all components containing a Null. This would be helpful in other situations where a definition isn't performing as expected because of the presence of a Null value within a longer list.

-Scott

Permalink Reply by David Rutten on March 4, 2014 at 10:05am

To everyone here;

Do you have Weaverbird installed,
and -if yes- does it start working once you uninstall Weaverbird?

David Rutten

david@mcneel.com

Permalink Reply by David Rutten on March 4, 2014 at 2:15pm

At any rate, it wasn't Giulio's fault, the bug just happened to surface with Weaverbird. Giulio did suggest a good fix and I'll release asap. Note, the data in the files is there, it was purely a problem parsing it. If you open files with internalised data in 0.9.0071 they should load correctly.

David Rutten

david@mcneel.com

Permalink Reply by Andrei Raducanu on March 4, 2014 at 3:08pm

sorry i didn't reply in time, i was out. should i check if it works without weaverbird or is everything already cleared up?

Permalink Reply by David Rutten on March 4, 2014 at 3:35pm

I think it's all cleared up.

David Rutten

david@mcneel.com