PPPeter Posted November 14, 2022 Share Posted November 14, 2022 If an artistic text object has empty lines at the end the bounding box only shows the visible part. The same goes for v1 but in v2 the invisible part can overlap other objects. Designer_wIigBqIOLy.mp4 Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted November 29, 2022 Staff Share Posted November 29, 2022 Hi @PPPeter, I've now logged this with the development team for resolution. Quote Link to comment Share on other sites More sharing options...
4dimage Posted November 29, 2022 Share Posted November 29, 2022 This is how this similar artistic text error looks like in Publisher. In contrast to frame text with artistic text the content should never exceed the bounding box. If i convert the art text to frame text the textframe automatically expands to include the last line Quote Hardware: Windows 11 Pro (23H2, build 22631.3880, Windows Feature Experience Pack 1000.22700.1020.0), Intel(R) Core(TM) i9-14900K @3.20 GHz, 128 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440. Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas. Link to comment Share on other sites More sharing options...
PPPeter Posted May 24, 2023 Author Share Posted May 24, 2023 Not fixed in 2.1.0 😔 Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted May 24, 2023 Staff Share Posted May 24, 2023 11 minutes ago, PPPeter said: Not fixed in 2.1.0 😔 Sorry it's taken me some time to come back to this, i've just checked up on the logged issue and it's been determined as by design, Artistic text bounding boxes are only intended to cover visible text and will not include any non-visible characters such as spaces/line breaks. For example, the shape of the bounding box will change to cover descenders whereas a standard text frame's bounding box will not. MikeTO 1 Quote Link to comment Share on other sites More sharing options...
PPPeter Posted May 29, 2023 Author Share Posted May 29, 2023 On 5/24/2023 at 9:09 AM, NathanC said: Sorry it's taken me some time to come back to this, i've just checked up on the logged issue and it's been determined as by design, Artistic text bounding boxes are only intended to cover visible text and will not include any non-visible characters such as spaces/line breaks. For example, the shape of the bounding box will change to cover descenders whereas a standard text frame's bounding box will not. I don't know if you misunderstood the topic but the problem is not the bounding box only showing the visible text, have a look at the video again. The problem is that it acts like the invisible rows are there, the invisible part can cover underlaying objects. If you click the invisible part of the bounding box the box get selected. It can surely not be by design that if you click a random space in your design that accidently is covered by some invisible, non-predictable object is selected instead? It is only text that has this behaviour but if it would be by design this would also apply to objects cropped by a rectangle for example, no? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 29, 2023 Share Posted May 29, 2023 3 hours ago, PPPeter said: If you click the invisible part of the bounding box the box get selected. It can surely not be by design that if you click a random space in your design that accidently is covered by some invisible, non-predictable object is selected instead? How is that any different than putting an unfilled rectangle (or a rectangle with a 0% opacity fill) over other objects on the page, then trying to click on one of the covered objects to select it? The first click will select the top object (the invisible rectangle). To select an object under it you need to use a Ctrl+Click or other method to navigate down in the layer z-order, as described in the Help: https://affinity.help/designer2/en-US.lproj/pages/ObjectControl/select.html Quote -- 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 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
PPPeter Posted May 31, 2023 Author Share Posted May 31, 2023 On 5/29/2023 at 1:22 PM, walt.farrell said: How is that any different than putting an unfilled rectangle (or a rectangle with a 0% opacity fill) over other objects on the page, then trying to click on one of the covered objects to select it? The first click will select the top object (the invisible rectangle). To select an object under it you need to use a Ctrl+Click or other method to navigate down in the layer z-order, as described in the Help: https://affinity.help/designer2/en-US.lproj/pages/ObjectControl/select.html I would say it's a big difference since the invisible, clickable, area extends outside the bounding box. If you have a 0 opacity rectangle the bounding box would show exactly where the rectangle is. In the text box the invisible area is totally unpredictable. This error was introduced in v.2 and I have a hard time thinking it is by design since it's not consistent with how other contained objects work. walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted May 31, 2023 Share Posted May 31, 2023 10 hours ago, PPPeter said: This error was introduced in v.2 and I have a hard time thinking it is by design since it's not consistent with how other contained objects work. As a work around I use the Move tool and Click Drag to select the 'un-clickable' text frame. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
Recommended Posts
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.