The undo button is too far from reset button

[xnuk]

Related repository: TinyWebEx/AutomaticSettings

Bug description

out.mp4

Let's say I made a mistake that I accidentally pressed the reset button. I expected some confirmation UI appears, but there was nothing. So I have to undoing options manually from my memory, and while doing it, I find there is actually 'Undo' button at the top of the settings page.

Steps to reproduce

1. In the settings page, click 'Reset all settings to defaults'
2. No confirmations or undo buttons is shown right at that moment
3. Panic

Expected behavior

An undo button or a reset confirmation should be in visible area at that moment, right after clicked the reset button.

Possible solution

I think replacing reset button to 'Undo' would be great, like clicking

[[ Reset all ]]

is replaced to

✔️ All are reset [[ Undo ]]

.

Or putting the toast message at the bottom is also okay I think?

[rugk]

That is a great idea and indeed a UX flaw. As you noticed, it needs to (or rather should) be implemented in https://github.com/TinyWebEx/AutomaticSettings/

Contributions are very welcome. I've also created an issue there to track it with more details of what I'd do implementation-wise: TinyWebEx/AutomaticSettings#28

[renji18]

Hey @rugk, I'd like to work on this issue as I start my contribution into open source.

[rugk]

Okay, great, please see what I've wrote before, that should give you the correct direction.

[TImmykiller5]

Can I still work on this?

[rugk]

As I saw @renji18 removed their assignment, I take this as a you for you @TImmykiller5. Anyway, feel free to work together/communicate here if something needs to be done etc.

So yeah, sure, you can take it. And thanks a lot in advance. If you have any issues or questions, e.g. how to implement a certain thing or how a thing works, feel free to ask. Also note GitHub's help can help on topics on how to use GitHub and e.g. how to create and update pull requests. Please also read our contributing guide to see how to get started with development and help us. And please read the past communication in this issue ans PRs to see what still needs to be done.