• Editor

  • New (useless?) warnings in Spine 3.6

    anglais
Related Discussions
...

Hi, ever since updating I've been getting this possibly harmless warning.
 Loading Image
My workflow is always to have the spine project in a folder along with an export folder in that folder; keep things nice n tidy.
So like "Player/Player.spine", "Player/export/"

Is there a reason not to do this? Or how do I get rid of this warning ' ^'

I'm also having another new warning
 Loading Image
I hide the Hurtbox and paths because I don't need to see them in the editor and they get in the way. But I need them to be there ingame, of course; and they still are after hiding the slot. Is this intended?

It's just a little annoying having to click 2 more times now after the update.
But otherwise amazing update, the clipping really helped me with a few projects. Keep up the great work ' v'

I mean these are both useful warnings. But Nate's open to suggestions for exceptions to them, I'm sure.

1.
It's only harmful for people who want to run texture packing on that "Player" folder, 'cause the "export" subfolder would get included in packing process.
For you, it should be no problem, unless you actually plan to do that.

2.
This is for people who forget that they hid some slots, which can result in the export looking different than what you see in the editor. We've seen this enough times and figured it warranted a warning, but also hopefully improve the UI to clearly communicate this state in the Tree itself: that a. slot visibility is not exported and b. some slots are disabled so some attachments may be hidden where they wouldn't be hidden in the export.

In your case, since they're non-renderables, the editor shouldn't be so uptight about it.

In case you needed another way to quickly show/hide paths and boxes:
 Loading Image
The "Others" row actually corresponds to those. If you turn of selection and visibility, you get the same effect, but it does so for all boxes and paths and a bunch of other non-renderable types, not just per-slot.

@Nate should the warnings not be emitted if the slots active attachments are non-renderable?

I think your idea to not warning about non-renderable attachments is a good one. Can you add an issue, pretty please? :heart:

Oh thanks for the feedback . w. probably should've used another word than "useless" mby a bit rude :B
But yea that exception would be nice - my problem is I do want to see my players hitbox that they use to attack with, but not their hurtbox.
In my mind there could maybe be options to silence certain warnings, like you said that first warning isn't applicable to me, but for some people it's useful. Or maybe have it once per project, and if you press yes on the warning, you wouldn't see it anymore in that project file.

Well, they really were factually useless for you, the user. 🙂 I also agree they aren't useful for everyone.
Nobody was hurt with the description. :p

I used to arrange my folders the same way too, if I didn't just completely have a separate parent folder for all the exports.

Adding more checkboxes to the Settings is really Nate's call. He likes to minimize their number since it can easily turn the Settings window into a murky swamp of checkboxes. Though we did talk about an about:config -like page for Spine at some point.