warn on app exit if unsaved changes?

[davidblackuk]

It's too easy to quit and loose changes in Fuji. We could auso save, but that might lead to configs not being what they should be.

It would be great to have a dialog that pops up on exit if the systems service says changes exist, something like

You have unsaved changes, blah, blah, do you want to

                   [Cancel] [Save and Quit] [Quit]

[hunsra]

@davidblackuk I looked into this and while it's possible to do in WinUI through the use of a lifecycle event, it appears to be impossible in Mac Catalyst. I found this article: https://developer.apple.com/forums/thread/678101 that indicates it's not possible to prevent a Mac Catalyst app from terminating. Do you know of a way to do this?

[davidblackuk]

@hunsra I don't know of a way to do this on maccatalyst. I'll move the issue back to the backlog. As the link says we might want to think about auto saving, but that's quite a big change in operation.

Another approach might be to maker the fact that there are outstanding edits more obvious. Perhaps an indicator on the save button (say a red exclamation mark) and change the tooltip to You have unsaved changes

What do you think of that?

BTW, i'm working on a keyboard settings pane ATM, I want to get it in a decent place so I can merge with your changes.

[hunsra]

@davidblackuk, I've actually done something like a "dirty" indicator in the long-ago past and it at least gives the user an idea of the state of things. The button color and/or exclamation might be enough. You could also consider changing the title bar text and color of the application to indicate unsaved changes so it's even more obvious, which is what I did in the past with an ancient VB app.

Another approach, perhaps even in addition to the indicator, is to actually persist the "unsaved" changes in a separate place from the truly saved changes. That way, when the app is started again, the unsaved changes are present. There would need to be a way of knowing the unsaved changes where reapplied and a way to discard them to be able to move forward without them if no longer wanted. Maybe just ask the user at startup if they want the unsaved changes from the last run applied or not. Just a thought.

[davidblackuk]

Have added a dirty indicator on te save systems button. So i'll close this for now