Nested Type errors

Questions & Answers
1

A quick note for Unity Answers…

The following is a post I made on an Ouya developer forum. Per advice I made an upgrade to the Ouya SDK to take care of an issue, and it brought up another issue. I typically have been dealing in JS, whereas the problem referenced here deals in all C# files, so this might be an easy fix for someone who’s more familiar with C than I am. After doing a lot of searching on the web I realized there wasn’t a ton of info regarding this error pertaining to my specific case, and so in addition to asking for help in the Ouya forums, also chose to seek the Unity family’s wisdom. Thanks for your help, patience, and understanding. God bless.

Original post:

Hello everyone,

Because of the progress that had been made on the project I’m working on I was hesitant to upgrade the ODK (Ouya SDK) since upgrading tends to bring with it tons of new frustrations. Yesterday I finally upgraded and immediately regretted it. After fixing various java errors that left my head spinning, I’ve got 60 compiler errors (of the same type) that I’ve not been able to figure out. To summarize them, they say:

“Assets/Plugins/IOuyaController.cs(31,13):
error CS0426: The nested type
KeyEnum' does not exist in the type OuyaSDK’”

That goes for the Ouyacontroller.cs file, Xbox360 controller, you name it. I looked in the OuyaSDK.cs file and sure enough, there’s no mention of KeyEnum anywhere. I admit though, that after 15 hours of bug fixing maybe my brain is just too fried to see it.

As an experiment, yep, I did at one point delete all the files throwing errors, and that did remove the warnings, but unsurprisingly that gave me zero controller use.

Incredibly frustrated, since this project is so close to release. Had one thing to implement that the new ODK was required for. (at least I hope. Will be incredibly upset if that thing isn’t fixed by the upgrade, but we’ll see)

On the old ODK, my Unity controller inputs just worked. I would love to go back to that simplicity. At the very least, I’d like to get rid of the errors. Sorry if this has something that’s been covered, I’ve been searching since yesterday and haven’t found a direct answer anywhere, though it seems like I come close at times. Thanks, and God bless.

2

It’s not helpful that you didn’t post which SDK(legacy/new) you are using for ouya. If look into the old(legacy) github project and in the OuyaSDK.cs, i find:

...

public enum KeyEnum
    {
        NONE = -1,
        BUTTON_O = OuyaSDK.BUTTON_O,
        BUTTON_U = OuyaSDK.BUTTON_U,
        BUTTON_Y = OuyaSDK.KEYCODE_BUTTON_Y,
        BUTTON_A = OuyaSDK.BUTTON_A,
        BUTTON_LB = OuyaSDK.BUTTON_LB,
        BUTTON_LT = OuyaSDK.KEYCODE_BUTTON_L2,
        BUTTON_RB = OuyaSDK.BUTTON_RB,
        BUTTON_RT = OuyaSDK.BUTTON_RT,
        BUTTON_L3 = OuyaSDK.BUTTON_L3,
        BUTTON_R3 = OuyaSDK.BUTTON_R3,
        BUTTON_SYSTEM = OuyaSDK.BUTTON_SYSTEM,
        BUTTON_START = OuyaSDK.BUTTON_START,
        BUTTON_SELECT = OuyaSDK.BUTTON_SELECT,
        BUTTON_ESCAPE = OuyaSDK.BUTTON_ESCAPE,
        AXIS_LSTICK_X = OuyaSDK.AXIS_LSTICK_X,
        AXIS_LSTICK_Y = OuyaSDK.AXIS_LSTICK_Y,
        AXIS_RSTICK_X = OuyaSDK.AXIS_RSTICK_X,
        AXIS_RSTICK_Y = OuyaSDK.AXIS_RSTICK_Y,
        BUTTON_DPAD_UP = OuyaSDK.BUTTON_DPAD_UP,
        BUTTON_DPAD_RIGHT = OuyaSDK.BUTTON_DPAD_RIGHT,
        BUTTON_DPAD_DOWN = OuyaSDK.BUTTON_DPAD_DOWN,
        BUTTON_DPAD_LEFT = OuyaSDK.BUTTON_DPAD_LEFT,
        BUTTON_DPAD_CENTER = OuyaSDK.BUTTON_DPAD_CENTER,

        BUTTON_BACK,

        HARMONIX_ROCK_BAND_GUITAR_GREEN,
        HARMONIX_ROCK_BAND_GUITAR_RED,
        HARMONIX_ROCK_BAND_GUITAR_YELLOW,
        HARMONIX_ROCK_BAND_GUITAR_BLUE,
        HARMONIX_ROCK_BAND_GUITAR_ORANGE,
        HARMONIX_ROCK_BAND_GUITAR_LOWER,
        HARMONIX_ROCK_BAND_GUITAR_WHAMMI,
        HARMONIX_ROCK_BAND_GUITAR_PICKUP,
        HARMONIX_ROCK_BAND_GUITAR_STRUM,

        HARMONIX_ROCK_BAND_DRUMKIT_GREEN,
        HARMONIX_ROCK_BAND_DRUMKIT_RED,
        HARMONIX_ROCK_BAND_DRUMKIT_YELLOW,
        HARMONIX_ROCK_BAND_DRUMKIT_BLUE,
        HARMONIX_ROCK_BAND_DRUMKIT_ORANGE,
        HARMONIX_ROCK_BAND_DRUMKIT_A,
        HARMONIX_ROCK_BAND_DRUMKIT_B,
        HARMONIX_ROCK_BAND_DRUMKIT_X,
        HARMONIX_ROCK_BAND_DRUMKIT_Y,
    }

...

if i hit up the newest, they have refactored the code and no longer use that KeyEnum. Have you ‘updated’ the SDK lately, did you remove old assemblies(dll’s) that may be confusing unity?

In their commit to github 700dbf5025793e15b0fa450dc670c8608290fd6f is when they removed it from the file(back in may). The commit message just said “More cleanup of legacy code.”. This isn’t a unity problem, i’m sure they are probably relying on the unity controller system.