-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visible action to reset animo demo #135
Comments
Okay, changing the User experience wise, the |
Changing a character requires you to receive a new set of starter credentials, so that's why it's currently resetting the whole demo in that flow (there is an issue open to fix this #13). If i understand correctly, you mean reset as in resetting the use case so you can re-do it? Currently, there is an option for this in the ctrl + k menu, but maybe we can change it so you can hover over the checkmark of the use case and than re-do it. It will clutter up the user's wallet with more of the same credentials though as we can't delete them from a user's wallet. |
Yes, I mean resetting just a use case. Can there be a work around to avoid the same credentials to be clutterd in the user's wallet? If no, we can leave the usecase resetting and then focus on just resetting the character demo So this is my point: We can have the reset button opposite the text with a red font. Sounds cool? |
We can't really do anything about the cluttered credentials in the user's wallet, but its not that big of a problem. If you complete the use case it currently shows like this: Maybe we can keep it like this and just add a rewind icon in there and allow users to redo the use case. There is nothing actually prohibiting users from redoing a use case, besides some information in the state about what use cases are completed. |
I think we should consider having a reset button for a particular Demo in case a user wants to retake the demo.
My suggestion is either putting a notice of what the
ctrl
+k
command does or simply putting a reset button for easy access.The text was updated successfully, but these errors were encountered: