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

    Moving the whole content of a layer

    Scheduled Pinned Locked Moved Resolved Issues
    4 Posts 3 Posters 5.0k Views 3 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.
    • Devil DinosaurD Offline
      Devil Dinosaur
      last edited by

      Hello everyone,
      It may be the way I do and not a bug.
      When I select a layer by clicking the circle in the layer panel, I expect its whole content to be selected as well. It works to copy/paste or resize the content but each time I try to drag it somewhere and move it in the canvas, only one object is selected and move. I tried to put my cursor inside the rectangle that defines the selection but not above an object but nothing at all happen then.
      What is the trick in order to select the whole content of a layer then move it somewhere in the canvas ?
      Thank you.

      Fred.
      MacBook Pro (M1) - MacOs Sonoma 14

      VectorStylerV 2 Replies Last reply Reply Quote 1
      • b77B Offline
        b77
        last edited by

        This was asked here a few days ago:

        https://www.vectorstyler.com/forum/topic/1610/ability-to-copy-all-objects-selected-using-the-circle-icon-in-layers-panel

        MacBook Pro (Intel) running Monterey 12.6.4

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

          @Devil-Dinosaur Looks like a bug (clarified from the earlier post).
          When the layer is selected, the click+drag will not detect it and will select an object.
          I added this to the backlog, and will try to find a fix ASAP.

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

            @Devil-Dinosaur This problem should be fixed in build 1.1.024

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