loukash Posted May 29, 2021 Share Posted May 29, 2021 Publisher v1.9.4.1076 & 1.9.3 Also affects Designer 1.9.4.2 & 1.9.3 and Photo… El Capitan, MacBookPro9,1 MacOS language English with Swiss German number formats, Affinity language English US Shapes that have been converted to text frames are missing font selection options from the context toolbar. apu_converted_text_frame_toolbar_bug.mp4 GRAFKOM and sbe 2 MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
walt.farrell Posted May 29, 2021 Share Posted May 29, 2021 Just focusing on the first item you converted: Are you clicking on it with the Move Tool, or double-clicking? On Windows, if I simply click on the Shape Path Text object, I still have the Move Tool, and so the Context Toolbar shows only the options for the object with a Move Tool. However, if I double-click the Move Tool switches to the Artistic Text Tool, and then the Context Toolbar changes to have all the text-related options (Font, etc.). -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
loukash Posted May 29, 2021 Author Share Posted May 29, 2021 1 hour ago, walt.farrell said: Are you clicking on it with the Move Tool, or double-clicking? The Move tool. I should have mentioned that, thanks. Double-clicking will then always show the whole shebang. But the point (bug) is that selection of a text frame with the Move tool won't show all applicable attributes depending on how the text frame was created. MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
walt.farrell Posted May 29, 2021 Share Posted May 29, 2021 31 minutes ago, loukash said: But the point (bug) is that selection of a text frame with the Move tool won't show all applicable attributes depending on how the text frame was created. But the attributes in the Context Toolbar are associated with the Tool, not the object. Until you double-click on the converted object you're not using a Text Tool, and that may not be a bug. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
loukash Posted May 29, 2021 Author Share Posted May 29, 2021 10 minutes ago, walt.farrell said: that may not be a bug It is a bug. This part of the context toolbar is simply missing, and there's no rationale for that: GRAFKOM and lepr 2 MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
walt.farrell Posted May 29, 2021 Share Posted May 29, 2021 1 hour ago, loukash said: It is a bug. Still not convinced, because the contents of the Context Toolbar are largely dependent on the Tool you have selected, and in your screenshot you don't have the Text Frame Tool selected, as far as I can tell. Also, you do not have a Text Frame active, as (I believe) you have a Shape text object, not a Frame text object. Here's what I get in the Layers panel, for example: So you're assuming you know that a Shape Text object should have on the Context Toolbar when the Move Tool is selected. It may simply be different from what a Frame Text object has there. Or yes, maybe there is a bug. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
lepr Posted May 29, 2021 Share Posted May 29, 2021 47 minutes ago, walt.farrell said: It may simply be different from what a Frame Text object has there. As @loukash said, there is no rationale for that difference. What sensible reason can you think of for the particular missing controls to be deliberately absent? Link to comment Share on other sites More sharing options...
loukash Posted May 29, 2021 Author Share Posted May 29, 2021 Walt, again: The point is that stuff that is missing is literally just "cut off" arbitrarily from the toolbar. There is no rationale why to hide the left part of the toolbar when a shape has been converted to text frame: Why then display the missing parameters if the same shape has been converted to curves before converted to text frame? Or why even display the parameters if you select two of the same shapes that won't display them if you'd select just one? It doesn't make any sense whatsoever. It's a bug. Accept it. GRAFKOM and thomaso 2 MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Staff Gabe Posted June 3, 2021 Staff Share Posted June 3, 2021 Hi all, It is indeed a bug. I'll get it logged. lepr and loukash 1 1 Link to comment Share on other sites More sharing options...
loukash Posted October 29, 2021 Author Share Posted October 29, 2021 Not fixed in 1.10.3 yet. MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Recommended Posts