data conversion failure on (deserialized) custom type

Hello All,

Has anyone ever run into trouble working with custom data types after (ostensibly successful) deserialization?

I have a type that survives internalization (stored persistently in Data below):

And appears to survive deserialization on reopening the definition, but then somehow fails one step downstream:

The error balloon reports a data conversion failure from Grid to Grid (where Grid is the type). A bit odd given that the Data param and panel are unfazed, no?

The type is written to and read from a byte array. Any thoughts?

Thanks,

Jon

Replies to This Discussion

Permalink Reply by David Rutten on December 21, 2015 at 2:30am

I'll need to see code to replicate this. But I'm out of office starting an hour from now until after Christmas so I won't be able to look at it until then.

Could it possibly be that there are two Grid types loaded? I know it's unlikely, but it's the first thing that pops into my mind when conversion fails from one type to ostensibly itself.

Permalink Reply by Jon Sargent on December 21, 2015 at 8:14am

Thanks for the reply, David. I don't think there are duplicate types, but I'll prod further. No rush on the code examination -- I'll send along a sample in a few days if it doesn't sort itself by then.

Happy holidays!

Jon

Permalink Reply by Jon Sargent on December 27, 2015 at 11:33am

Issue resolved / user-error confession:

In the unlikely event this happens to someone else, try double checking that you've inherited from GH_PersistentParam :)

RSS