Hardcoded Paths Prevent Moving the Library

Issue #109 resolved
Ryan Medeiros
created an issue

We attempted to migrate the Odin Inspector plugin to a different directory (we like to wrap external code into NuGet packages). This caused a few problems:

1) GeneratedOdinEditors.dll gets recreated at a set path and prevents proper code compilation with our moved version. 2) .asset files are generated at Assets/Plugins/Sirenix/Odin Inspector/Config if they don't exist (regardless of whether they exist elsewhere) 3) Image data fails to load which causes exceptions that prevent the library from operating correctly (e.g. Assets/Plugins/Sirenix/Editor/Icons.png is loaded via its absolute path).

We've dealt with this a bit in our other code if some ideas would help. Most notably you can have inspector-assigned properties on the scripts themselves that are available to the editor.

Comments (4)

  1. Tor Esa Vestergaard
    • changed status to open

    Odin should detect its own path in the project and use that, so long as you are only moving the Sirenix folder around, and not renaming the Sirenix folder, and ideally not rearranging the contents of the Sirenix folder either.

    If you haven't done any of those, but just moved the Sirenix folder around, untouched, I'm afraid we'll need a bit more details, as I've just tested it and failed to replicate your error.

  2. Log in to comment