Jump to content

Recommended Posts

Posted

Exactly what the title says. This has been an issue I've had with Photo for a while but it's getting more and more annoying as time goes on. Is there any way for me to disable this? The following image is from an entirely black document but with a white brush active (not used) over the canvas. I do not want this. I can not picture a situation where anyone would want this to be the default behaviour.

Note: solutions like "switch tools before copying" or "move the brush off the canvas" are not what I'm looking for here. I am aware of those solutions, but I feel they should not have to be part of my process when all I want to do is press ctrl+shift+c like I would in most any other image editor without this happening.

image.png.a4698b599d65366abc5facd282362960.png

Posted

Change the key order
<ctrl><shift>C causes the problem

<ctrl>C<shift> works, I have no idea why

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Posted
2 hours ago, David in Яuislip said:

Change the key order
<ctrl><shift>C causes the problem

<ctrl>C<shift> works, I have no idea why

For me, <Ctrl>C<shift> copies only the brush preview, and none of the rest of the document.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5

Posted

Must be witchcraft, I've just checked again and it works as I wrote
Here's another oddity, white brush in the centre of the canvas, <ctrl><alt><shift>E for Merge Visible
The thumbnail in the Layer panel shows the white brush blob

MergeVisibleOddity.png

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

Posted (edited)

To say that ctrl+c+shift causes all sorts of problems would be an understatement. 99% of the time, it only copies. As in, the same thing as if you were entering ctrl+c. The obvious reason for this is that it is registering ctrl+c as an input before the shift modifier unless you are exceptionally fast. So far, I've managed to get this to work once. If I try shift+ctrl+c, I get the same problem as if I entered ctrl+shift+c.

Keystroke order does not solve this.

Edited by Psilocervine
Posted
1 hour ago, Hens said:

This also solves nothing. I can change it to any combination of keystrokes I want, for instance I tried ctrl+', and it still copies the brush if it's on the canvas.

It is clear that this is an issue with the copy flattened functionality itself, and I will hazard a guess that it's actually tied to how Affinity Photo handles rendering the brushes on top of the canvas to show where they are when in use.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.