Chris B

I think "(Best)" is being used here as the best balance between speed and quality (so "best performance"), although I can see that you might well assume (Best) meant "Best Quality"

In that case, Hangman was spot on. You were seeing the app do a '2nd pass' which can be distracting. I'm glad it is sorted! 

In that case, Hangman was spot on. You were seeing the app do a '2nd pass' which can be distracting. I'm glad it is sorted! 

Hi @DarkClown,
The Affinity apps use the display technology (MipMaps) to achieve good performance.
I think (but could be wrong) what you're seeing is 'screen redraw', rather than the area getting darker. It looks as though the section beneath the brush is momentarily blurring before the full-resolution image is redrawn beneath the brush position as you move the brush around the screen...

@Chris B The setting was on "Automatic (Best)" - but changing retina quality to "High Quality" solves the problem.
Frankly I assumed that "Automatic (Best)" equals "High Quality" .... apparently I was wrong

@anto we've now logged this - thanks!

@anto we've now logged this - thanks!

It looks like the behaviour in Publisher is broken - I was doing the testing in Designer on WIndows. We'll poke this further.

It looks like the behaviour in Publisher is broken - I was doing the testing in Designer on WIndows. We'll poke this further.

It looks like the behaviour in Publisher is broken - I was doing the testing in Designer on WIndows. We'll poke this further.

Hi all,
I have just logged this as a feature request. I've asked to either add the Vector Crop Tool as an option that we can add from Customise Tools or potentially add a Vector Mask option with the existing mask options.

I'm proposing this as a bug because while the QR Code generator library (used in the v2.5 Beta for QR Code creation) supports the vCard (.vcf), VCALENDAR and VEVENT (.ics) formats it's not possible to create QR Codes with the Affinity apps using either format since both require a CRLF (Carriage Return/Linefeed) after each line entry which the single-line Payload format used for QR Code creation in the Affinity apps don't accept and means the following formats fail:
\n = LF (Line Feed) → Used as a new line character in Unix/Mac OS X \\n = An escaped LF (Line Feed) → Used as a new line character in Unix/Mac OS X \r = CR (Carriage Return) → Used as a new line character in Mac OS before Mac OS X \r\n = CR + LF → Used as a new line character on Windows %0a = a URL encoded (Line Feed) → Used as a line feed character on Unix/Mac OS X %0d = a URL encoded (Carriage Return) → Used as a carriage return character on Unix/Mac OS X %0d%0a = a URL encoded (Carriage Return/Line Feed) → Used as a carriage return/line feed character on Unix/Mac OS X %0d%0a%0d%0a = a URL encoded form of CRLFCRLF → which tricks the server into inserting a CRLF sequence on Unix/Mac OS X This means that while it is possible to create a vCard QR Code with the QR Code generator library using this format:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Apple Inc.//macOS 12.7.4//EN
N:LasteName;FirstName;;;
FN:FirstName LasteName
ORG:Company;
EMAIL;type=INTERNET;type=WORK;type=pref:name@company.com
TEL;type=WORK;type=VOICE;type=pref:Work Number
TEL;type=CELL;type=VOICE:Mobile Number
ADR;type=HOME;type=pref:;;Address
NOTE:Notes
item1.URL;type=pref:Web Address
item1.X-ABLabel:_$!<HomePage>!$_
BDAY:2000-02-28
END:VCARD
or an 'Add to Calendar' VEVENT QR Code with the QR Code generator library using this format:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:Spatie calendar-links
BEGIN:VEVENT
UID:90bbafd033c512f7590d844a0d65b449
SUMMARY:Run the London Marathon
DTSTAMP:20240421T080000Z
DTSTART:20240421T080000Z
DTEND:20240421T130000Z
DESCRIPTION:I'm running the London Marathon
LOCATION:London
END:VEVENT
END:VCALENDAR
it's not possible to create a QR Code using the Affinity apps because of the single-line format which results in a No Usable Data Found error message when scanning the generated QR Code using the iPhone camera's built-in QR Code Scanner...
Note: I've not tested this on Android but my assumption is that this will result in the same issue...

Steps to reproduce
create new file in RGB/32 (in V1, create RGB/16 and then convert to RGB/32) create a rectangle over full canvas set black to white gradient (from default swatches) switch between ICC managed and unmanaged. Expected:
rendering must differ. ICC managed shows „normal“ gamma 2.2 gradient, „unmanaged“ shows typical gamma 1 gradient Observed:
rendering is always „icc managed“ Tested on M1 IPad (2020) with V1 (correct rendering) and V2 (2.4.2 beta and retail, wrong rendering)
RPReplay_Final1713373061.mov RPReplay_Final1713373041.mov

Full Keyboard Access is an option in macOS System Settings (aka Preferences in older versions). Just search Settings/Preferences for "full" and you'll find it.
The other thing Chris suggested is in Affinity's Settings. Go to Affinity Photo 2 > Settings (or Affinity Designer 2 or Affinity Publisher 2, depending on which program you're using) and in Settings click Shortcuts on the left side. Check if you assigned Space to any shortcut. Of you can just click Serif Defaults to restore your shortcuts to the original state which will fix the issue if this is what you did. Others have done this before by accident while editing their shortcuts.
Good luck.

It looks like Comic Sans to me. 
Please check what you have set in Full Keyboard Access inside System Preferences or you don't have Space set as a shortcut in the app.

Hey NotMyFault,
I agree this is a bug - on desktop, selecting another tool will commit the 'Align' History entry and I would want this behaviour on iPad too. I will get it logged. Cheers  

Hey NotMyFault,
I agree this is a bug - on desktop, selecting another tool will commit the 'Align' History entry and I would want this behaviour on iPad too. I will get it logged. Cheers  

If you try to distribute multiple layers in both x and y direction, the tool resets always if you switch to another tool. The result is lost.
 
RPReplay_Final1712863765.mov

@Hangman both Sean and I have reproduced this with our own User folders on Windows. I've attached it to the bug report for the developers to review. We're just currently trying to track the actual cause down.

I have logged this against Monterey and mentioned the fact I can sort of reproduce it on Sonoma if I make the grid enormous

I do not see this problem on Ventura.

Well, I did see it on Sonoma initially. However, we have seen a few Monterey-specific issues lately - or at least issues have been easier to reproduce on Monterey. I will try this again in the office on Monday but can happily still log the bug.

Thanks Hangman - I will get this logged.

A minor cosmetic issue but when using the Data Merge tool in the 2.4.2.2371 Beta the grid layout is missing when the grid is initially drawn, i.e., the rows and columns are only shown on mouse release...

Data Merge Grid.mp4

Hi Chris,
thanks for the analysis - i can only confirm, that i tried it in the 2.2.1 and it is the same - so, very probably, we found an older bug....