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

    Difficulty selecting object with selection warp when it sits overtop another object

    Scheduled Pinned Locked Moved Resolved Issues
    4 Posts 3 Posters 4.7k 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.
    • BoldlineB Offline
      Boldline
      last edited by

      I've noticed when I have a shape sitting overtop other shapes, it can be very difficult to select the top shape with the selection warp tool. I have to move the shape away from other shapes and then click on it to apply the warp feature.

      Here is an example where it happened in my work.

      I tried it again in a new document using basic shapes for both - a large shape behind and then placed a smaller shape in front of it and had the same result

      0_1643735492303_10ff4dad-54e0-4c5a-8f3b-2ea5a89b3ddf-BLD 2022-02-01 at 12.11.06.png

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

      S VectorStylerV 3 Replies Last reply Reply Quote 0
      • S Offline
        Subpath @Boldline
        last edited by

        @Boldline

        Dont know if this really helps.
        But as a temporare Workaround
        how about to use a clone for that.

        Here a video:
        https://recordit.co/cP0nR0X53X

        Win 11
        CPU: AMD Ryzen 5 9600X, 6-core.
        GPU: Nvidia Geforce RTX 5070.

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

          @Boldline This looks like a bug, will get fixed (but maybe not in the next build).

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

            @Boldline This problem should be fixed in build 1.1.024

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