- Bearbeitet
replacing path in every skin
Hi!
I have 1 skeleton with 3 skins: same character - 3 different outfits. The thing is I started linking some images from skin A and reusing them at the skin B and C (these are common features, like mouth, nose, etc), and also some of the images are linked from the skin B just to the C and so on... (sorry, I'm learning... so some of my files are made a mess). And now I need to use images coming just from the corresponding skin, so I had to duplicate these common images in every skin folder. But once I rename the image path it changes in all the skins, so if I go to skin A and rename the image path to eg.: outfit-a/images/mouth seems everything ok, but once I check in the B and C skins I can tell it has also changed the path to outfit-a...
Hope I had explained it clearly
Thank you so much for always helping me 
Hello, are you changing the image path from the image node?
Images - Spine User Guide: Images node
Try to use a general images path, and then have a subfolder for every skin.
If you need to change the path for the specific skin, you can use the find and replace function, check that only the selected skin is affected (scope), change only the path (Field: Path), and then replace the name to point to the right folder.
Tree - Spine User Guide: Find and Replace
Hi Erika, thanks for answering,
I have a subfolder for every skin and I did that already with the find and replace, but there are 2 images that give me the problem. These are the only 2 images that have been duplicated... one is a dash and the other is a small shiny circle, so I needed them more than once at the same time. And when I go to find and replace window with the "current skin" checked doesn't find it.
You could also try to select them and then choose "Tree selection" 
when i do that it changes to the same path in all the skins, and same if i try with the entire project scope
This is what i write in the window so you can see where's my mistake :doh:
Note that you also have a Scope option called Current skin. Current skin will only include the currently active skin, it sounds like this is what you are after.