I encounter an issue that all the checkboxes "select" for all bones would become unchecked.
I'm not referring to enable/disabling the bones, it's on.
I believe that there is a hotkeys I accidently press to make this happen, because I can redo and redo until the settings back to normal again.
I cannot find anything in the hotkey documents that refer to this function, and this annoying me a lot.
I have 200+ bones many of them are constraints or reference bones, so I have to tweak those I want to be selectable every time it happens.
All bones become unselectable issue
What version of Spine are you using?
The Select checkbox definitely shouldn't become unchecked by itself. If it does, it's a bug, but it's not something we've seen recently. It could have been a bug long.
The only way to uncheck Select for all bones would be to select them all and uncheck it. There is no hotkey to do that.
When the Select property of the bones is changed, it could get added to the undo state, so that would explain why undo can get you back to having Select checked. In the latest code the property is set very few places and there doesn't appear to be a way for it to be set when it shouldn't be.
Nate
Thanks for reply, I just encountered it again.
I'm using latest 4.2 version, I can see if I have the logs for this issue.
This is the log file I just opened, the same thing happen right after.
I have tweak the hotkeys-1.tx, but I believe this is the only things I changed:
"Local Axes: shift + L
Parent Axes:
World Axes: shift + W"
I think this might happen after I select all by ctrl+A, and hit some hotkey that might lead to uncheck all the select boxes.
spine.log
849B
hotkeys-1.txt
8kB
There are no hotkeys that can change the bone Select checkbox, so that can't be it.
Thanks for the log. It shows some warnings for extremely slow filesystem access. It looks like it's for an audio folder. You can set the path on the Audio node in the tree to something that doesn't exist or maybe to the images path, since that doesn't seem to trigger the warning.
All we can say at this point is to try to change the audio path so that warning goes away, otherwise to try to keep an eye out for what actions you took just before the problem occurs -- maybe that gives some clues.