Using Orion with LeapCSharp.NET3.5 dll instead of LeapC folder?

Tags: #<Tag:0x007fb6d499bf28>

damocles 2016-02-29 09:04:51 UTC #1

I want to use the LeapCSharp.NET3.5.dll included in the Orion SDK in my Unity project and could use some guidance. The new integration imports a LeapC folder with the raw .cs scripts instead of the DLL, and when I place the LeapCSharp.NET3.5.dll in my plugins folder I get errors from what appear to be overlap in function/class declarations with the new scripts. Deleting the LeapC folder seems to eliminate those overlaps, but causes another exception related to missing Leap Internals.

Is there a way to use the dll instead of the LeapC scripts?

Missing LeapCSharp.NET3.5.dll

Barrett-Fox 2016-02-29 19:44:22 UTC #2

The LeapCSharp.NET3.5.dll is not compatible for Orion or a replacement for its included LeapC.dll's and the Leap CSharp wrapper code which is contained in the /LeapC folder. The LeapCSharp.NET3.5.dll will be deleted from the next release of our SDK.

damocles 2016-02-29 20:27:49 UTC #3

Ah, thanks for letting me know. The reason I ask is because I'm using a plugin that hasn't been updated for Orion yet, and I have access to the source code and can quickly recompile it using the LeapCSharp.Net3.5 dll but I'm not sure how to compile it for use with the new structure/LeapC folder. I might have to abandon it for other solutions because the developer appears to have stopped working on it recently.

Joe_Ward 2016-02-29 22:39:13 UTC #4

To see how hard it would be to recompile, just remove LeapCSharp.NET3.5.dll from the project. Unity should then list all the places that no longer compile.

damocles 2016-03-01 02:24:58 UTC #5

Thanks, I'll give that a shot and report back.

zachkinstner 2016-03-06 00:12:17 UTC #6

@Joe_Ward, I'm curious about the move away from the Leap DLL. For my Hover VR project, I found it very useful to have the Leap DLL -- I could reference it in my own libraries, using a separate VS solution, and keep the code out of the Unity project itself.

I realize that this isn't the most "Unity-centric" way to do things. I just prefer to drop versioned DLLs into my Unity projects, rather than pasting all the code directly into it.

For Hover VR, this approach helps to keep the installation clean, because there are several optional libraries (for different UI components, input devices, etc). The developer simply chooses which Hover DLLs to include in their project.

Any chance we could see LeapC provided as a DLL instead?

(Tracking this for Hover VR at https://github.com/aestheticinteractive/Hover-VR-Interface-Kit/issues/41).

Joe_Ward 2016-03-07 01:28:22 UTC #7

There isn't a strong reason not to build the files into a dll, other then to help developers understand what was going on by having the source available. We'll discuss whether we want to make the change and figure out the ramifications, if any.

Thanks for letting us know that there was a use case we weren't considering.

swt 2016-03-10 01:34:57 UTC #8

It is probably best to release both the source code and precompiled dlls.

Joe_Ward 2016-03-10 01:36:08 UTC #9

We plan to release both in the SDK, but only the compiled .dll in the Unity assets (otherwise there would be name conflicts). (We have a few build issues related to Unity's ancient version of .NET to sort first, though.)