4dimage Posted August 15, 2023 Share Posted August 15, 2023 1) Thanks😁 The refined Windows panel appearence looks so much clearer now 👍 The Windows issue with the truncated labels still exists. The panel persists the column width of the left label-column at least during one user session. But after app restart the column width is reset to default and the labels are truncated again. In consequence the user has to resize the column once for every user session to read the truncated parameter names. Would be helpfull, if the last user defined column width could also be persisted like the panel size. 2) I can't rename a custom field - maybe this is intended behaviour ? Steps: a) I add a custom field to the palette with some inital value (German translation missing). OK so far. b) Now i edit the field by clicking the button "Edit Custom Field" (German translation missing). The flyout dialog shows the text input with the current field name selected. It appears as if i could change the name. But as soon as i press any letter key the flyout dialog closes without letting me type into the input. If the field name may not be changed afterwards, the input might be disabled to indicate that the name is immutable ? Quote Hardware: Windows 11 Pro (23H2, build 22631.4317, Windows Feature Experience Pack 1000.22700.1041.0), Intel(R) Core(TM) i9-14900K, 32 Core@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...
MikeTO Posted August 15, 2023 Share Posted August 15, 2023 7 minutes ago, 4dimage said: b) Now i edit the field by clicking the button "Edit Custom Field" (German translation missing). The flyout dialog shows the text input with the current field name selected. It appears as if i could change the name. But as soon as i press any letter key the flyout dialog closes without letting me type into the input. If the field name may not be changed afterwards, the input might be disabled to indicate that the name is immutable ? I'm seeing the same issue on macOS Ventura. Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.1, MacBook Pro 14" (M4 Pro) Link to comment Share on other sites More sharing options...
walt.farrell Posted August 15, 2023 Share Posted August 15, 2023 Also on Windows. 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 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Staff Chris B Posted August 16, 2023 Staff Share Posted August 16, 2023 I'll get the missing translations logged as well - thanks! Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted August 17, 2023 Staff Share Posted August 17, 2023 An issue raised in this thread ("Can't rename custom field") has now been reported to the developers by the testing team (Ref: AFB-8227). Thank you very much for reporting this issue to us. Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted August 23, 2023 Staff Share Posted August 23, 2023 The issue "Unable to rename Custom Field Variable names" (REF: AFB-8227) has been fixed by the developers in internal build "2.2.0.1971". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Andreas CH Posted August 26, 2023 Share Posted August 26, 2023 In der Version 2.2.0.1971 fehlt immer noch die Übersetzung. Dann habe ich noch zwei weitere Stellen gefunden. Quote 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.