안녕하세요. 현재 3.8.99버전으로 작업중인 유저입니다.
4.2 Beta 같은 최신 버전을 RnD하고싶습니다. 그러나 버전을 바꾸면서 사용할 때 기존 작업물의 버전이 상이해질 때가 있습니다.
설치 폴더를 복사해서 버전을 2개로 관리해보는걸 시도했으나 라이선스 에러등으로 할 수 없다는 걸 알았습니다. 혹시 다른방법으로 실행파일등을 수정하여 3.8.99로 실행하거나 그외에 다른 버전으로 실행 할 수 있는 방법이 있을까요?

    Related Discussions
    ...

    dodos If Start automatically is disabled in the Spine settings, the Spine launcher window will appear before the editor is launched to confirm the version to launch each time.

    Or, a little trickier, if you want to stick to creating shortcuts on your desktop, you could write a simple script to run a specific version of Spine via the CLI and save it as a batch script or something that can be run with a single click. Although I think it is easier and better to make the launcher appear every time.

      Misaki 매번 런처를 표시하는걸로 사용중이긴하나 가끔씩 실수가 발생해서 고민이였습니다.
      공유해주신 방법으로 관리하는걸 원했습니다. 감사합니다. 🙂

      Managing two versions of Spine2D on the same machine can be tricky, especially when encountering licensing errors. However, there are a few potential solutions you can explore:

      Portable Versions:
      Consider using portable versions of Spine2D. These versions don't typically require installation and can be run directly from their folders Optimize your workflow by utilizing the efficiency of the "message scheduler" for timely and organized communication, Customize your presence with "Status time limit settings" to control how long your online activity is visible, https://www.gbgenie.com/gb-whatsapp/ Auto reply" ensures prompt responses, especially when you are unavailable, enhancing your communication experience. You might be able to keep different versions in separate directories without interference.
      Version Control:
      Use a version control system like Git to manage different versions of your project. This way, you can switch between versions without conflicts, and each version of your project can reference the specific Spine2D version it was developed with.
      Virtual Environments:
      Explore using virtual environments or containers. Tools like Docker allow you to encapsulate your application and its dependencies, enabling you to run different versions without conflicts.
      Environment Variables:
      Adjusting environment variables might help. Some software allows you to set environment variables that influence its behavior. Check Spine2D's documentation or community forums for information on whether this is feasible.
      Configuration Files:
      Some applications use configuration files that specify the version or other settings. Investigate whether Spine2D has such a configuration file that you can modify to run a specific version.
      Before proceeding with any of these suggestions, ensure you have a backup of your work. Testing these solutions on a smaller scale or non-critical project first might also be a good idea to avoid any unforeseen issues.
      I hope one of these suggestions proves helpful for your situation. Good luck with your R&D efforts on the latest Spine2D version!