Included GoKit crashes with ArgumentOutOfRangeException error after deleting tweens

[SpaceCadetEve]

I keep a list of looping tweens with the intention of deleting them when the object is removed from the stage. After deleting them, GoKit gets a crash in Go.handleUpdateOfType.

I think this was fixed here: prime31/GoKit#38

It might be as simple as getting the latest GoKit, creating a new .dll, but with the limited time I spent trying to upgrade my own version, I doubt it will be the simple.

[jpsarda]

You can include the latest source of GoKit in your project and remove the dll, this should work.
But note that the latest version of GoKit has renamed every classes ( all starting with Go now ), so that will take some time to rename everything in your project.

[SpaceCadetEve]

I tried that, renamed things, and got to where MonoDevelop 4 (using Unity 4.3) complains about default parameters. I know I can switch the projects to use .NET 4, but Unity likes to keep regenerating the project files when I add new files and I lose those settings. Unless, I'm missing something to make the .NET stick. I think this vexing issue is why Matt has the .dll (at least based on something I read on the unity forums posted in 2012 :P).

On Jan 11, 2014, at 5:34 PM, Jean-Philippe SARDA [email protected] wrote:

You can include the latest source of GoKit in your project and remove the dll, this should work.
But note that the latest version of GoKit has renamed every classes ( all starting with Go now ), so that will take some time to rename everything in your project.

—
Reply to this email directly or view it on GitHub.

[MattRix]

Yup, that's why I use the dll (though it's worth noting it's only an issue if you compile in monodevelop). I've seen workarounds to make the .NET setting stick, but none of them have actually worked for me unfortunately. I should see if I can figure that out.

I should also really update the GoKit dll, it's been a while since I did that, but it's actually a bit of a pain to build it properly... I forget exactly what caused the issues, but last time I did it, building it in monodevelop just didn't work and I ended up having to build it in VS instead.

[jpsarda]

Oh I didn't know about this problem. I'm using a custom version of GoKit with Unity4.2 and it compiles fine in both MonoDevelop and Unity. If I understand correctly, If I upgrade to Unity4.3 I'll get problems when compiling in MonoDevelop.

[MattRix]

No this was an issue long before Unity 4.3. (well back into Unity 3) Basically when Unity creates the csproj files, it sets the .Net target as 3.5 (which doesn't support default parameters) even though Unity supports most .Net 4 faetures. So when you compile in monodevelop (aka having "build in monodevelop" set to true), you get errors on methods that use default parameters.