Hi, When you say adding a new "thing" are you able to clarify what you are referring to? Jess
Adding a new month/entity type/property/color etc., in "Settings" has no "Cancel" option, unlike when you're adding entities in the sidebar. There is only a "Delete" option at the bottom, which I agree doesn't make much sense when nothing has been created yet.
Hi, I have modified this behaviour in version 0.9.2 which has just been submitted. The top-left 'Back' button that was disabled until you typed a valid name is now enabled as a Cancel button while the text field is empty (or invalid). Tapping this button when it says 'Cancel' will abort the creation as you would expect. However, if you type text, it reverts to its current status as a 'Back' button that will create the entity type (or other thing), and the Delete button becomes the only way to delete it. I think this is probably the best compromise. The alternative would be for the top-left button to always function as a Cancel button, and the top-right 'Done' button to become an 'Add' instead, such that both buttons take you back to the previous screen... but I think I prefer the approach where the top right is always 'Done' and dismisses the modal. I am happy to be convinced otherwise though, so have a play with the new version and let me know if it still feels too counterintuitive and we can try the alternative as described.
Sorry for the lack of detail in my original post! So the "Back" button and the "Done" button do the same thing? It would be more consistent with the UX of other apps, if you kept "Cancel" as a consistent button and there was only one way to confirm creation of the entity. Things shouldn't be deletable until they've been created and the "Delete" button is better placed only in swipe menus and edit screens.
In the new update, the top left button switches between either "Back" or "Cancel" depending on whether the name item name is valid. So when it is blank, it says Cancel, when it is valid it becomes "back". Top-right Done always saves all changes, and closes the entire modal window. That is what I have Implemented in 0.9.2 for everyone to test, and to see if it needs further tweaking. It is difficult either way because those buttons act as navigation as well. Right now, the assumption being made is all valid edits are intended and retained on backwards navigation under normal use. We are only really looking at something different in the "Create new XXX" use case. The alternative when creating a new thing is for top-left to always be Cancel, and top-right to be "Add and go back a screen" as opposed to "Save and Close entire modal window" which it is as present across all screens. This would mean you need to navigate back to the main screen before you can actually exit the modal.
Okay so, looking at 0.9.2: - Adding a new character has a persistent Cancel button. - Adding a new entity type gets a back button the minute you start typing. I would expect this kind of behaviour to be consistent across the entire app. I can understand the need for Back buttons when adding properties e.g. Birth/Creation, but would expect Okay/Cancel style UX for creation of the overall Entity/Character/Thing.