Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.
Search the Community
Showing results for tags 'AFB-5632'.
-
With large UI font selected, descender of fonts is cut in layers panel. macOS Ventura 13.0.1 with no accessibility settings enabled etc. etc.
-
Cropped layer names with 'Large' Font UI Size
Floor posted a topic in Designer 2 Bugs found on macOS
The layer names in the layer panel are cropped when the Font UI Size is set to Large. The descenders are not visible. Steps to reproduce: Enable Preferences > User Interface > Font UI Size > Large Create a new layer named 'typography' Result: 'typography' is shown in layer panel, but descenders are cropped off, see screenshot -
First of all, congrats on the release of the new version. I got excellent value from Designer v1, so was happy to pay again. I am looking forward to playing with the new features. I noticed a minor glitch in text display in the Layers pane. Descenders get chopped off at the baseline. See the "g" and the "y" in this screenshot: Hopefully it won't be too hard to fix Best wishes Will
-
In the captions of the layer window the g and other letters are cut in half. See screen shot.
-
Greetings. Just to let you know that when the UI Large font is selected the descenders of the letters in the layers labels are cut off, pink looks like oink - ha ha just realised that's appropriate in a weird way. But I digress, the text box needs making taller to accommodate all the letters. Just saying.
-
This one layer is not showing any adjustment layer icons when collapsed. Notice the comparison between open and closed. And other layers. Also, at my current UI font settings, the lower part of some lower case letters are cut off.
- 3 replies
-
- affinity photo v2
- bug
-
(and 1 more)
Tagged with:
-
Photo version 2 on my mac cuts off descenders on my layer names and shortens window tab names when using the "Large" Font UI Size option in preferences. The default option displays properly. This was not an issue in version 1.