hawk Posted November 23, 2021 Posted November 23, 2021 Version: 1.10.4 (latest) Reproducible: Yes It happens with new documents (new files). Modified documents that are based on opened image files (not .af* project files) are not saved after hopping from one Affinity app to another. Example steps: Open an image file like PNG in Affinity Photo. (Optional: make some edits.) Select Edit in Designer... (Optional: make some edits.) Select Save (⌘S), or close the document (⌘W) and in the prompt click the Save button. Actual result: the Save command seems to fail silently. The original file is untouched, no new file can be found, and no error message, bell, or notification is raised. When the document is closed, your work can be simply lost. Expected: the changed document should be written to the original file (flattened) or I should be prompted to make a choice. In most other macOS apps, issuing ⌘S on unsaved work either writes back to a file, or produces a prompt without fail. At the very least there would be an alert sound (and screen flash if configured) for unrecognized or unavailable keyboard shortcuts. macOS 12 Monterey -- Designer, Photo, and Publisher are equally exhibiting this behavior. Quote ♥️Affinity v2; macOS 14; ⌨️🖱; recreational user since 2014.
Old Bruce Posted November 23, 2021 Posted November 23, 2021 This has been reported and noted. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
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.