When activating the AP window brush strokes

[srg]

hope I can explain. It happens when I am working on a mask and when AP is open and another window is active. When I want to re- 

 

activate AP by clicking on the AP window, the brush leaves a stroke instead of waiting for AP to be activate by the click. 

I  had a recording but cannot upload it

This bug is very annoying because after 

[MikeTO]

Hi @srg, I understand what you're saying and agree with you but please let me rephrase it for others.

Clicking an inactive window for a Mac app should activate it and bring it to the front, nothing else should happen. With Affinity, it also acts on that click as if it was already active which can be confusing. You might accidentally create an object or change an attribute depending on where you clicked.

It doesn't affect me that much because I use Affinity at full screen size so I generally only activate it with Cmd+Tab, but if you use a larger monitor and Affinity doesn't take up the full screen it can be confusing. I agree it should be fixed.

[walt.farrell]

I know that Windows works as you say macOS should. How do non-Affinity applications handle this on macOS?

I ask because, if I remember correctly, Linux and Unix systems can be configured to allow interaction with the visible parts of application windows that are behind other application windows. 

And as macOS is kind of a Unix system, perhaps it allows that mode of operation, too?

[MikeTO]

54 minutes ago, walt.farrell said:

I know that Windows works as you say macOS should. How do non-Affinity applications handle this on macOS?

I ask because, if I remember correctly, Linux and Unix systems can be configured to allow interaction with the visible parts of application windows that are behind other application windows. 

And as macOS is kind of a Unix system, perhaps it allows that mode of operation, too?

It's good to know it works better on Windows, it's just a Mac-specific bug then. There is no setting to change this interaction.

Mac apps from Apple, Adobe, and Microsoft adhere to the Mac standard and activate the window and bring it to the front but don't perform another action with the same click like Affinity does.

It's not clear where this direction is in Apple's current guidelines so I can't link to a page. They removed a lot of the basics in recent years and assume you just know it. Here's what it said in the very old days when everything was spelled out.

When a user clicks in an application window, the click activates the window, but makes no other changes. To make a selection in an application window, the user must click again. This behavior protects the user from losing an existing selection when the window becomes active. When the user activates a window that had been deactivated, reinstate the window just the way it was before the window was deactivated.

[srg]

1 hour ago, MikeTO said:

It's good to know it works better on Windows, it's just a Mac-specific bug then. There is no setting to change this interaction.

Mac apps from Apple, Adobe, and Microsoft adhere to the Mac standard and activate the window and bring it to the front but don't perform another action with the same click like Affinity does.

It's not clear where this direction is in Apple's current guidelines so I can't link to a page. They removed a lot of the basics in recent years and assume you just know it. Here's what it said in the very old days when everything was spelled out.

When a user clicks in an application window, the click activates the window, but makes no other changes. To make a selection in an application window, the user must click again. This behavior protects the user from losing an existing selection when the window becomes active. When the user activates a window that had been deactivated, reinstate the window just the way it was before the window was deactivated.

It is important to note thatthis bug is not present in V2.1. Only on the V2.2 beta

[EmT]

Hi @srg
We are aware of this issue and I've passed along your report to the devs. 

[woefi]

Today I saw a newer post by @srg regarding this issue but decided to instead reply to this original one as it already has two Bug tags on it: 

APL-1434 and AF-1159 (which was already reported in April of 2023)

Affinity, please get to it.

I just realized I _mentally_ put on my heat gloves when handling affinity apps in these scenarios.