Forums | Moodkie Interactive

The method inside the class is meant to be:

public TreeNodeSerializedWrapper() { }

Not:

public void TreeNodeSerializedWrapper() { }

.. as it's meant to be the constructor.

You can create a new .cs file, or you can add the class to an existing .cs file, whichever is easiest for you.

Once you've carried out all of the steps you should be able to delete it anyway. It's only used so that we can generate an ES3Type with the correct fields.

Ahh I see, it's strange that they've created a serialise method which doesn't actually serialise the data. Generic classes aren't currently supported in the Easy Save 3 beta as we're only testing core functionality at the moment. You can however manually add support for them by creating a non-generi...

Hi there, The problem is that you're using an external serialiser to get your class as a byte array (or possibly a string?), but then you're still trying to save this byte array to the file with the type List<TreeNodeSerialized<TNT_PlaylistLine>> . If you change your ES3 lines to use byte[] as the g...

Hi there,

I've never heard of anything like this happening before.

Would you be able to create a very basic test project which replicates the error and PM me the link and instructions to replicate it?

All the best,
Joel

Hi there, If you don't specify a tag, it will delete the entire file. See the documentation for more info: http://docs.moodkie.com/easy-save-2/playmaker/playmaker-actions/delete-action/ In Easy Save 3 you can use the Delete File action: http://docs.moodkie.com/easy-save-3/es3-playmaker/es3-playmaker...

Hi Adam,

Thanks for the bug report. This has already been fixed in the latest update which is currently on the Asset Store's approval queue.

All the best,
Joel

It was indeed that page which helped me solve the error originally, but that's for sending it my way anyway

All the best,
Joel

Hi there, It looks like you've discovered an edge case in C# where a using block won't dispose of it's underlying stream if an exception occurs in it's constructor (despite Microsoft's own documentation mentioning nothing about this). It's an easy fix at our end and will be resolved in the next upda...

Think less of writing a bool as a string, and more for writing classes with similar properties without having to convert between them beforehand. We can use reflection to find out what fields on the object parameter match those found on T, and then write the available fields to the file as T.