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

    Shift-X does not swap fill and stroke settings when the pen, pencil, brush, etc is selected but no line is yet started

    Scheduled Pinned Locked Moved Resolved Issues
    4 Posts 3 Posters 4.9k 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 Online
      Boldline
      last edited by

      I noticed that when I have any of the pen, brush, pencil, line tools selected but have yet to add a mark on the document with it, I am unable to use the shortcut "shift-x" to swap between the fill and stroke settings. I have to make a mark and then afterward, I am able to swap the settings with that keyboard shortcut.
      Ideally, the stroke and fill could be swapped at any time.
      Often I am starting a new pen path for example, and the fill is on and no stroke. I see this before I begin using the pen tool and I want to adjust it prior to making the path, not just after. I currently have to use the cursor to click the arrow between them. Using the shortcut would be preferable.

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

      b77B VectorStylerV 3 Replies Last reply Reply Quote 1
      • b77B Offline
        b77 @Boldline
        last edited by b77

        @Boldline Yes, I reported this in Ncic's thread about working with the Pencil tool.

        MacBook Pro (Intel) running Monterey 12.6.4

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

          @Boldline Fix will be in the next build!

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

            @Boldline This issue should be fixed in build 1.1.062

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