VectorStyler
    • Categories
    • Unread
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Immediate crash on committing modified Application Shortcuts

    Scheduled Pinned Locked Moved Bugs in VectorStyler
    5 Posts 2 Posters 4.3k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      JuurGroove
      last edited by

      I’m unable to customize keyboard shortcuts in version 1.2.049. I mapped F1 and F2 to Zoom Out and Zoom In and the program crashes immediately after clicking Ok in the Application Shortcuts window. Repeated this crash several times, restarted the whole system, repeated again. It also happens when I do not change any keyboard shortcuts at all but just select Restore to Defaults from the presets menu, and once again upon clicking Ok the program crashes.

      VectorStyler 1.2.057 | macOS Sequoia 15.2 | MacBook Pro 14" M1 Pro/16GB (2021) | XPPen Artist Pro 16 (Gen 2)

      VectorStylerV 2 Replies Last reply Reply Quote 0
      • VectorStylerV Offline
        VectorStyler @JuurGroove
        last edited by

        @JuurGroove This might be a regression, will fix it ASAP.

        1 Reply Last reply Reply Quote 1
        • VectorStylerV Offline
          VectorStyler @JuurGroove
          last edited by

          @JuurGroove Can be replicated here also. It only occurs when opening the shortcut editor with a shortcut

          J 1 Reply Last reply Reply Quote 0
          • J Offline
            JuurGroove @VectorStyler
            last edited by

            @VectorStyler Yes, selecting it from the menu works, thanks!

            VectorStyler 1.2.057 | macOS Sequoia 15.2 | MacBook Pro 14" M1 Pro/16GB (2021) | XPPen Artist Pro 16 (Gen 2)

            VectorStylerV 1 Reply Last reply Reply Quote 1
            • VectorStylerV Offline
              VectorStyler @JuurGroove
              last edited by

              @JuurGroove The fix will be in the next build.

              1 Reply Last reply Reply Quote 1
              • First post
                Last post