• Bugs

  • BoundingBoxFollowerInspector issue

    英語

  • SoulGame

    • 投稿 #1
    • 編集済み
    • この投稿は英語で投稿されました
    Related Discussions
    ...

    To continue with Unity Editor issues, here is a weird one. On a BoundingBoxFollower component, every time I click on the Slot drop down list and select a Slot, I got :

    Destroying assets is not permitted to avoid data loss.
    If you really want to remove an asset use DestroyImmediate (theObject, true);
    UnityEngine.Object😃estroyImmediate(Object)
    Spine.Unity.BoundingBoxFollower:ClearColliders() (at Assets/spine-unity/Modules/BoundingBoxFollower/BoundingBoxFollower.cs:131)
    Spine.Unity.BoundingBoxFollower:HandleReset(SkeletonRenderer) (at Assets/spine-unity/Modules/BoundingBoxFollower/BoundingBoxFollower.cs:88)
    Spine.Unity.Editor.BoundingBoxFollowerInspector😮nInspectorGUI() (at Assets/spine-unity/Modules/BoundingBoxFollower/Editor/BoundingBoxFollowerInspector.cs:52)
    UnityEditor.DockArea😮nGUI()

    I speculate it is adding an additional GameObject as child without being able to remove the previous one...? In any cases, after clicking several times and refreshing the Project windows I end up with a bunch of copies. Here is what it looks like: (HeroDefense is the GameObject with the Spine stuff on it)

    HTTPS をサポートしていないため、画像は非表示になっています。 | まだ表示する


    And where it starts to be weird is that when I drop the prefab in the hierarchy, all the copies are not there... :smoke:

    • Pharan

      • 投稿 #3
      • この投稿は英語で投稿されました

      Are you editing the component in the prefab?
      I didn't write it but I think this inspector wasn't designed with that in mind.
      I'll take a look.

      Yep, that's editing from the Prefab.

      • Pharan

        • 投稿 #5
        • この投稿は英語で投稿されました

        Might take me a while to get to this. I read through the code and it's a bit extensive.
        For now, I recommend putting the prefab in the scene temporarily to edit it, and then applying the changes from there.

        Will probably fix it within the week. Thanks for taking the time to report all these editor problems. :yes:

        I'm fixing this but there are some lingering (harmless) inspector warnings caused by internal Unity code that I can't get rid of.
        I've added some messages in the inspector too, to clarify what the checkboxes are supposed to do, and I've hidden the checkboxes if they don't make sense to be shown (eg, on a prefab).

        Should be part of the unitypackage update tomorrow.