Can't internalise groups

@David Rutten

Is there a specific reason why the group parameter wont allow internalising data? If you put them in a more generic data parameter you can internalise and it works, but only if it stays in the same document. As soon as you copy it over into a new document, it shows them as "Group with 0 objects".

In original file, also shows no internalise for groups:

Copied to a new file:

Is this just a bug or is there a specific reason?

Regards,

Armin.

Replies to This Discussion

Permalink Reply by David Rutten on March 26, 2017 at 4:24am

Groups don't know how to read and write themselves from and to files. They are made up objects of potentially unknown type, each of which might also not be able to (de)serialize itself.

I did write some code that lamely tries to do its best when confronted with a similar situation, but at present that code only helps the Generic parameter.

You'll have to internalise the data before it goes into the Group component I'm afraid.

Permalink Reply by Armin Seltz on March 26, 2017 at 6:03am

Thanks for your explanation. I don't really need the internalising for groups, but just noticed it when trying to make a small patch for a different forum post and thought it might just be a bug. I was using groups for the first time as it made data management much easier and the groups are just a bunch of curves in each group. I guess I'll have to figure out the data structure to work without groups, but this one is a tough one (hex-grid having weird double-column logic, but needing rows instead, BBText needing all text flattened, whole grid divided into sections, etc..).

Permalink Reply by David Rutten on March 26, 2017 at 9:10am

I agree that it is a bug that Groups go empty when they are inside a Generic parameter. And I guess once I fix that the additional steps required to make group parameter internalisable will be few.

Thanks for pointing it out, I'll see if it makes sense to invest the time in GH1 to fix this.

RSS