- Змінено
Strange problem with saving
I've been using the program for about 2 months and haven't run into this problem before but just encountered it. Usually when trying to save as a new file the file browser window pops up and everything works fine (though scary as the spine window minimizes) but this time it opened up and looked slightly different (smaller and more... basic I guess? Looks more like safe-mode windows with no anti-aliasing on the text etc.) I can see the text cursor blinking for me to type a new file name so it doesn't seem to be frozen, but nothing is interact-able and I can't cancel out either. Has anyone run into this problem before? I'd like to be able to not lose an hour of work if possible considering it was extremely tedious weight painting.
Thanks!
Edit: I figured out how to get out of the window. Ctrl-alt-del and ending the save window task. Unfortunately it still happens every time I save-as making it so I can't save as a new file anymore. This sucks because I usually save a back up every time I save.
What version of Windows are you using?
Are you using any downloaded window-management or graphics-related programs that would override things in Windows?
Do you have a particularly old computer, have a small amount of RAM, or use unusual graphics hardware?
Also remember.
Spine 3.6 has an auto-save/auto-backup feature. The default setting saves your project every 15 mintes. But remember to save often anyway.
And note that Spine saves backups of previous manually-saved versions of your project in your Spine folder in case something does wrong like power loss or a crash.
The Spine window un-maximizes because otherwise in some situations the file dialog can get stuck behind the maximized window (thanks, Microsoft). When Spine fails to create the standard file browser, it falls back to using another kind of file browser. I guess that is what you see, though it's odd that you can't interact with it without some voodoo steps. One thing you can try is to hold shift before and during the opening of the file dialog. This prevents the fallback dialog. Maybe what happens is Spine incorrectly decides the normal dialog failed and tries to show the fallback dialog, then the normal dialog succeeds (or some other strange interaction like that, I wish we could reproduce the problem).