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

    Toggling the Transform panel from the panels menu hides or moves contextual menu bar instead

    Scheduled Pinned Locked Moved Resolved Issues
    3 Posts 2 Posters 4.5k Views 1 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.
    • BoldlineB Online
      Boldline
      last edited by Boldline

      I'm getting strange results each time I attempt to turn on the transform panel from the panels menu.

      The first time I did so, it moved the contextual menu to the bottom of the screen. I moved it back to the top and tried again - this time the contextual menu completely disappeared.
      I closed out VS and reopened - same issue again. I did a refresh and tried again
      each time I tried to open the transform panel, it now creates multiple copies of the contextual menu and no sign of the transform panel

      Resetting the workspace to default fixed the issue

      0_1649862268042_b35a514f-7939-4ce9-9690-d780bc5c01a5-BLD 2022-04-13 at 11.01.57.png

      UPDATE: If I turn on and off the transform panel a few times, it eventually shows up but the issues with the contextual menu continue regardless
      0_1649862868003_2a003fcd-63b3-412d-a93c-3c32a35f837b-BLD 2022-04-13 at 11.13.50.png

      🍎 macOS Tahoe 26.2, Mac mini (M1, 2020), Chip Apple M1, Memory 16 GB
      Cintiq 27QHD Display and LG Ultra HD Display

      VectorStylerV 2 Replies Last reply Reply Quote 1
      • VectorStylerV Offline
        VectorStyler @Boldline
        last edited by

        @Boldline I will add this to the backlog. If it occurs again, send me the workspace.xml file.

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

          @Boldline This problem should be fixed in 1.1.048

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