karlh Posted January 28, 2023 Posted January 28, 2023 I was working on a layout and got the message new version available. I did the upgrade from 2.0.3, where the export did work very well. no problem with the dictionary. Then the installation started and after that the export claims for the dictionary. Quote
walt.farrell Posted January 28, 2023 Posted January 28, 2023 First, I would suggest checking Preferences, Tools, and examining the setting for the Additional Dictionary Folder to make sure it looks correct, and then clicking Open to examine the contents of that directory and making sure all the directories (such as de_AT) are present. 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
karlh Posted January 28, 2023 Author Posted January 28, 2023 Hi Walt, you are right (of course). The parameterisation got lost when the update from 2.0.3 to 2.0.4 was performed. I remember when I had the problem in March 2022. I took screenshots from the installation and therefore it should be no problem to fix it. But maybe, you will report this behaviour to the developer of the installation process. The update should not destroy any existing parameterization. The update from 2.0.2 to 2.0.3 was working fine. Nothing got lost. Many thanks for the fast answer! Quote
walt.farrell Posted January 28, 2023 Posted January 28, 2023 9 minutes ago, karlh said: But maybe, you will report this behaviour to the developer of the installation process. The Serif staff will see this at some point, and take care of that. Was there anything unusual about the way you performed the update from 2.0.3 to 2.0.4? And were you updating using the MSIX version of 2.0.3 or the unofficial MSI/EXE version of 2.0.3? In any case, good to hear that it's resolved for you, and this may help someone else if it happens to them. 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Staff Pauls Posted February 2, 2023 Staff Posted February 2, 2023 was the app bought from the microsoft store or direct from Affinity? Quote
karlh Posted February 2, 2023 Author Posted February 2, 2023 I bought it direct. I moved the dict to the default dictionary folder. And all is ok now. I tried to answer immediatly to Walts post but I always get Error 403 cloudfront when answering. Br Karl Quote
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.