يتمّ عرض هذا الموقع بشكل أفضل في متصفّح حديث مع تمكين JavaScript.

How does skinField attribute work?

nicmar

I'm using this code to select a sprite and a spine attachment:

[Serializable]
public struct CustomizationSlotSetting {
   [PreviewField]
      [LabelText("")]
   public Sprite sprite;
      [SpineAttachment(skinField:"Front")] 
      [LabelText("")]
      public string spineAttachment;
}

In my spine file, i have two skins "Front" and "Side". I actually only use the front skin.
But when I use the code above, i get to choose from Null, Default, Front, Side. Did I miss any parameter?

I also tried currentSkinOnly=true, but no difference.
I'm using the IHasSkeletonDataAsset to get the skeletondata with this code:

public SkeletonDataAsset skeletonDataAsset;
public SkeletonDataAsset SkeletonDataAsset {
   get { return skeletonDataAsset; }
}

Any ideas? 🙂

nicmar

Harald

If you do not want to use the active skin (Initial Skin) at your SkeletonAnimation component, you cannot add a constant string here instead. The skinField parameter should not hold the constant skin name ("Front") but the name of the sibling property:

var skinProperty = property.FindBaseOrSiblingProperty(targetAttribute.skinField);
if (skinProperty != null) currentSkin = skeletonComponent.Skeleton.Data.FindSkin(skinProperty.stringValue);

So the solution is to add a sibling property as follows:

[SpineSkin]
public string skin="Front";
// alternatively you could also hide it in the inspector:
[HideInInspector] public string skin = "Front";

[SpineAttachment(skinField:"skin")]
public string attachment;

nicmar

Hi,
I tried your suggestion, and it still shows both null, default and Front like in my first screenshot.
I removed the Side skin as it wasn't used.
I also tried the SpineSkin attribute to make sure I didn't spell it wrong. Do you have any idea why it's not working?

[SpineSkin]
public string templateAttachmentsSkin = "Front";
[SpineAttachment(skinField="templateAttachmentsSkin")] 
public string attachment;

Harald

This sounds very strange. Did you test this at a minimal example as well? I assume that perhaps other code or components are perhaps interfering?