slajerek Posted March 13 Share Posted March 13 To replicate this bug: 1. Create image with some pattern and a layer. 2. Save image and reload. 3. Move layer only to a new position. 4. See that File/Save is not active, Ctrl+S does not work 5. Reload image and see that layer was not moved. A workaround for this is to use Save As instead of Save, but that can be overlooked quickly as even Affinity does not ask to save image on close even though it was modified (i.e. layer has been moved). Affinity Photo version 2.4.0 macOS Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted March 13 Share Posted March 13 26 minutes ago, slajerek said: Move layer only to a new position Physically on the screen, or within the Layers panel? What do you mean by a pattern, exactly? Can you share a sample file? Quote -- 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...
slajerek Posted March 13 Author Share Posted March 13 Here's a video that shows the issue: Quote Link to comment Share on other sites More sharing options...
Pšenda Posted March 13 Share Posted March 13 Video_2024-03-13_191158.mp4 Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130. Link to comment Share on other sites More sharing options...
slajerek Posted March 13 Author Share Posted March 13 Pšenda it looks you're using Windows, not macOS, and also one layer not two. Also do you use 2.4.0 version? btw. does it prove something that it works for you? For me not Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted March 13 Share Posted March 13 26 minutes ago, slajerek said: Here's a video that shows the issue: If I understand that video, you have not actually changed the file yet after reopening it. You have moved a pixel selection, but I think you'll see that no entry has been added in the History panel yet, as the operation is still in process and has not been finalized. You need to do something to finalize the operation, and then you'll see a Transform entry added to the History panel. And at that point, as the file has been modified, File > Save will be available. It is only available when the History panel is not empty, and has been changed since the last Save. To finalize the operation, you could: Switch to a different tool; or Click outside the image; or Remove the pixel selection (Cmd+D on Mac, or Ctrl+D on Windows). and probably some others I haven't thought of. Quote -- 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...
Pšenda Posted March 13 Share Posted March 13 (edited) 4 hours ago, slajerek said: and also one layer not two. You don't mention the problem with two layers in your initial post ("3. Move layer only to a new position."). However, moving with two layers makes no difference. Of course it could be an OS difference issue, but it's always good to confirm or deny. Try the same procedure with "move layer to new position" (your description was a bit vague) and see if the bug is related to your OS. Edited March 13 by Pšenda Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130. 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.