All Affinity applications: Warning Sound on saving (CMD/CTRL-S)

[D.VE]

If you hit CTRL-S and the document already has been saved there is a warning sound!

Could you please remove that? This is SOOOOO annoying!
I'm an IT guy therefore it is in my muscle-memory to hit CTR-S every couple of seconds. Nobody needs a warning, if the document is already saved. Especially if I use the publisher to actually documents, it drives me crazy.

thx

[MikeTO]

I probably save as frequently as you do but I actually like the beep.

[carl123]

I'm not getting a bleep on Widows 11

May be Mac specific

[Pšenda]

On 3/5/2023 at 10:36 AM, carl123 said:

I'm not getting a bleep on Widows 11

Yes, I can confirm - no beeping.

[retrograde]

Mac here. I'm not hearing any bleeps. Is it a preference or a system alert thing maybe?

[PaulEC]

I don't hear it on Windows 10 either!

I don't think it's an Affinity thing, I suspect there is some other common denominator with the people who do hear a beep. Windows has a whole set of system sounds, (I assume Mac has similar settings,) so I wonder if this sound may be down to a setting there?

[Pšenda]

1 hour ago, PaulEC said:

I don't think it's an Affinity thing

But only Affinity knows that file is unmodified, so there is no reason to save it. In Windows, the Save item/command in the File menu is disabled if the file is not modified. So, you cannot save file using the command from the menu, but the shortcut Ctrl+S will apparently remain active - for which there is no reason.

[PaulEC]

7 minutes ago, Pšenda said:

But only Affinity knows that file is unmodified, so there is no reason to save it. In Windows, the Save item/command in the File menu is disabled if the file is not modified. So, you cannot save file using the command from the menu, but the shortcut Ctrl+S will apparently remain active - for which there is no reason.

Good point! – it just seemed that there are so many options that can be enabled in Window's sounds that it was a possibility!

 

[PaulEC]

32 minutes ago, LondonSquirrel said:

Except there is something to warn about. File/Save or cmd S is not available to you if there is nothing to save. Try it with other commands which are also not available, for example Arrange/Move Back One (or cmd [) if there is nothing to move back. You will get the same alert.

I still don't get why only some people hear these sounds! There don't seem to be any sound/alert options within the Affinity software itself. If it is a bug, it's strange that it always happens for some people but not for others. I've tried various things, and nothing seems to generate any sounds within the Affinity apps! If other commands also generate the same alert it would be interesting to know how these alerts are enabled/disabled!

 

[PaulEC]

11 minutes ago, Red Sands said:

Go out in the spring sunshine and enjoy the good weather. I'm sitting outside in a garden during a break from gardening. Recommended.

I'm not sure why you find it necessary to be rude and dismissive if someone else dares to give their opinion about anything. but don't worry I'll be sure to avoid any of your posts in the future!

Please continue to insist that anything you don't like is a "bug", if it makes you happy!

[Pšenda]

1 hour ago, Red Sands said:

The rest of the world:

Only for interest - is menu item Save disabled or enabled, if is file unmodified? 

[MikeTO]

To clear this up, the system beep is an old school macOS standard. Apps are supposed to use the system beep when you choose a keyboard shortcut that isn't available. Open a new window in Safari and press Cmd+S, Cmd+C, Cmd++, Cmd+-, etc, and you'll hear the system beep. Open a new document in Pages and press Cmd+C and you'll hear the system beep. Etc.

The reason you're not hearing system beeps when saving already-saved files in Apple apps is Apple switched to continuous save a few versions back so there's no reason to ever choose the Save command in those apps. If you do choose Save, it will save the file even if it's already saved.

As for Microsoft and Adobe apps, I assume they've chosen to do away with the system beeps.

If you don't like the beep sound or volume, you can change it through System Settings > Sound. As for me, I like the beep because it tells me nothing was done, whether that's saving, copying, etc.

[MikeTO]

41 minutes ago, Red Sands said:

Then you might wonder why Apple Pages, Word, Photoshop and other programs do not play this sound when you save. There is no continuous saving involved in what I did.

LondonSquirrel and I have already explained why Apple apps such as Pages don't system beep when choosing Save for an already-saved file - every time you choose Save Pages will save the file again. I don't think you'd want Affinity to do that.

If you don't want to change the beep (alert) volume, you can change it to play over your computer's speaker rather than through your headset.

[Pšenda]

33 minutes ago, MikeTO said:

every time you choose Save Pages will save the file again. I don't think you'd want Affinity to do that.

And why not? The user requests to save the file (the reason may be to update the metadata and timestamp - perhaps for backup or SVN purposes), so there is no reason for the application to prevent him from doing so and saving made it impossible. If someone from Serif thinks that not saving an unchanged file is desirable (for example, to avoid unnecessary disk wear), then let them offer it as an option in Preferences. But the standard is to "execute" the requested command.

[MikeTO]

22 hours ago, Pšenda said:

And why not? The user requests to save the file (the reason may be to update the metadata and timestamp - perhaps for backup or SVN purposes), so there is no reason for the application to prevent him from doing so and saving made it impossible. If someone from Serif thinks that not saving an unchanged file is desirable (for example, to avoid unnecessary disk wear), then let them offer it as an option in Preferences. But the standard is to "execute" the requested command.

It's okay for simple apps like Pages because saving is virtually instantaneous, but with massive Affinity files I wouldn't want it to save when it doesn't need to. Plus, with the long-standing problems with cloud and network drives, saving is sometimes like playing roulette.

Going back to the OP's first post (who probably thinks we're all crazy for still discussing this), they said they have muscle memory for hitting save over and over again. I have muscle memory for it, too, and I like to know that Affinity has finished saving before I quit the app. So I'll hit Cmd+S twice, once to save and once to hear the confirmatory beep. I've been doing this for decades.

We each have our workflows and our own quirks, I'm no different. My point is this isn't a bug, it's the standard, and I'd prefer it to keep working this way. If you don't like it, please ask for a preference setting, not to have it taken away.

[D.VE]

Is there any news on the table? 

I started working with a graphic tablet... And this is sooooo annoying since it also appears if you select a tool that is already selected (with the settings "change tool with modifier key").

The key on my graphic pen selects the brush tool... I switch between mouse and pen a lot. So I normaly take the pen press the key and start drawing... Again it plays this annoying sound, if the brush tool is already selected... 

Drives me nuts.