Dear Spine Team,
Thank you very much for your detailed explanation and kind response. We now understand the technical constraints of using unadorned windows, and we appreciate you letting us know how you plan to improve the window system in the future. We look forward to Spine's continued development.
Enter

- 28 août 2024
- Inscrit 24 avr. 2024
- Modifié
Dear Spine Team,
Thank you for your great software. I would like to suggest two improvements when using it on Windows 10:
- ability to move windows by dragging the title bar after zooming in.
- when I click and drag the title bar after zooming in the spine, it doesn't move. For example, Photoshop, Unity, Chrome, etc. can be moved after selecting the title bar, which is convenient.
- support for windows snapping feature (resize and maximize windows)
- the window zooming to fit the monitor provided by Windows does not work. For example, in other programs, if you grab the title bar and move it to the left end of the monitor, it zooms to the left 1/2 of the monitor, or if you move it up, it zooms to the full size.
I think these features would greatly improve the user experience. Thank you for your continuous improvement and communication, and I look forward to following Spine's development.
Thank you.
Dear Spine Team
I wanted to inquire about the possibility of a feature that would allow users to separate windows within the Spine editor, similar to applications like Photoshop, Unity, or Visual Studio.
I believe that, given the power of Spine and the complexity that comes with it, having the option to externally reorder windows could greatly improve the user experience and workflow.
Are there any future plans to improve the editor, including the ability to detach windows and place them outside the main editor window?
Thank you for your time and the excellent work you do with Spine. thank you
In summary, my opinion is that it would be better to input the scale 0 value using the Tab key.
- Modifié
First of all, I apologize for any misunderstandings I may have made. I also realize that my previous explanation was not entirely accurate. I often change both scales x and y when working.
Therefore, I enter a value for x and then use Tab to move to y.
For example, if you change [1,1] to [2, 3], you can type 2 in x -> Tab -> 3 in y.
However, if I change the value from [1,1] to [0, 0], it is not possible to enter 0 for x -> Tab -> 0 for y.
If I enter 0 in x and press the Tab key, the value of x does not change to 0 and the value stays the same and moves to y.When using Enter, it seems to have been inconvenient to change x to 0, click y again, and then change it to 0.
Thank you for your time
I understand that there are concerns about the ambiguity and potential for errors that could arise from including 0 in the scales x and y.
However, entering 0 does not change the value itself. It would be more convenient if entering 0 would change the value to a number close to 0, such as 0.0001. It seems cumbersome to have to enter 0.0001 manually each time.Thank you for always providing quick updates and answers. I appreciate it.
I imported a 16-bit PSD file in version 4.2.08.. but,
"Unsupported PSD color depth. PSD files must use 8-bit color depth."
I'm working on a 16-bit image. Can't I use the PSD import function?