Darner Posted December 17, 2024 Posted December 17, 2024 So so bad... Re-designed a file in Affinity Designer. Open a document with an old version of this re-designed file. Where it is an Embedded link. Changed from Embedded to Linked file. This apparently overwrites and change the new re-designed file, into the old embedded design. So new re-designed file is gone...seems like just overwritten without any notice, no way to retrieve. Also like to remind about the bug as written before, where the time stamp of "Created" of all Affinity files, gets changed into same date as "Modified". Quote
carl123 Posted December 17, 2024 Posted December 17, 2024 10 minutes ago, Darner said: This apparently overwrites and change the new re-designed file, into the old embedded design. Did you not get a warning like below Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Darner Posted December 17, 2024 Author Posted December 17, 2024 Just now, carl123 said: Did you not get a warning like below Unfortunately no kind of warning Quote
carl123 Posted December 17, 2024 Posted December 17, 2024 I'm on Windows and always get that warning If someone on a Mac could replicate it then that may help, what Mac OS are you on? or if you can supply a recipe that does it every time that may also help track the problem down Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
walt.farrell Posted December 17, 2024 Posted December 17, 2024 46 minutes ago, Darner said: Re-designed a file in Affinity Designer. What kind of file? 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
Darner Posted December 17, 2024 Author Posted December 17, 2024 1 hour ago, walt.farrell said: What kind of file? .afdesign file pure vector walt.farrell 1 Quote
Darner Posted December 17, 2024 Author Posted December 17, 2024 1 hour ago, carl123 said: I'm on Windows and always get that warning If someone on a Mac could replicate it then that may help, what Mac OS are you on? or if you can supply a recipe that does it every time that may also help track the problem down Sequoia 15.1.1. Believe the original feedback can work as a recipe. Quote
Darner Posted December 17, 2024 Author Posted December 17, 2024 1 hour ago, carl123 said: I'm on Windows and always get that warning If someone on a Mac could replicate it then that may help, what Mac OS are you on? or if you can supply a recipe that does it every time that may also help track the problem down Not much time for replicating anything right now as have to re-design the entire file that was lost Quote
Darner Posted December 17, 2024 Author Posted December 17, 2024 Adding to original topic issue. When opening a doc with linked file, the linked file does not appear until cklicking "Locate in document" in Resource Manager. Quote
Darner Posted December 22, 2024 Author Posted December 22, 2024 Another issue with Linked Files. Not working well with linked shadows, compared to the original shadow file. See attached. Same shadow same file. Just one is linked, one is original. Not biggest issue for most perhaps, but still indicates issues in general with linked files. Quote
walt.farrell Posted December 23, 2024 Posted December 23, 2024 21 hours ago, Darner said: Not working well with linked shadows, compared to the original shadow file. See attached. Same shadow same file. Just one is linked, one is original. I think we would need to see that Linked file, and the file you're using it in that illustrates that behavior. Can you share 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
Darner Posted December 23, 2024 Author Posted December 23, 2024 44 minutes ago, walt.farrell said: I think we would need to see that Linked file, and the file you're using it in that illustrates that behavior. Can you share them? It's just black layer with gaussian blur fx (around 10-20) in Affinity Designer. When trimming the link, it becomes an issue. Might say "just don't trim" or "don't lnk", but as working with multiple links as a workflow in some cases, not trimming or just pasting, makes it unnecessary complicated to work with. So this was intended for Affinity ppl to hopefully fix. Thanks for following up though!! Quote
walt.farrell Posted December 23, 2024 Posted December 23, 2024 39 minutes ago, Darner said: When trimming the link What does that mean? 40 minutes ago, Darner said: So this was intended for Affinity ppl to hopefully fix. Again, they'll probably need to see your files, or at least more complete screenshots to understand exactly what you're doing. 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
Darner Posted December 23, 2024 Author Posted December 23, 2024 2 hours ago, walt.farrell said: What does that mean? Again, they'll probably need to see your files, or at least more complete screenshots to understand exactly what you're doing. As mentioned in previous post: Linking a black layer with gassian blur fx (10-20(, the edge becomes cut as shown on attachments. Not sure what part here is difficult or how to explain it better. If you still don't understand that's fine, as the post is meant for reporting bug to Affinity. Quote
walt.farrell Posted December 24, 2024 Posted December 24, 2024 19 hours ago, Darner said: If you still don't understand that's fine, as the post is meant for reporting bug to Affinity. They will want to see screenshots, and possibly sample files. (See info in my reply to another of your posts.) There are things you could do in the outer file (the one including that linked file) that would affect this. Different color formats or color modes, adjustments applied that affect the linked file, etc. More information is always useful, to aid in recreation or to immediately see what the problem is. At least now we know more about what that linked file contains, but it would be even easier if you simply attached the file. Then someone trying to recreate the issue doesn't need to create the file. 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
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.