Skip to content
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

[RFE] upon opening entry present user with fields in view-only mode and button to enter edit mode #304

Closed
hgkamath opened this issue May 19, 2022 · 1 comment

Comments

@hgkamath
Copy link

hgkamath commented May 19, 2022

this was suggested in issue #303

Feature request

Description

Upon opening pre-existing entry from 'entry-list' activity-window, first take user to a 'view-only-mode' activity window. In this 'view-only-mode' window, the user should be able to view values of fields in non-edit-able view-only-label-fields and hence, should not be able to edit. An 'edit' button this 'view-only mode' activity window should then take user to the usual 'edit-mode' activity-window in order to edit/make changes. This usual 'edit-mode' activity-window then already has values in edit-able text-fields that can be modified as well as the 'back' and 'save' buttons. In most cases, the user is only wants to view fields. Only when the user wants to edit fields, should the user have to press the 'edit' button in the 'view-only-mode' activity-window to goto the edit-mode, where user can make changes, save changes and exit edit-mode in order to return to 'view-only-mode'. Another advantage of the 'view-only mode' is that the android keyboard won't keep popping up, while just reading-off or copying-off field-values.
This is a good feature to have even after fixing #303. and if fixed before fixing it, it definitely reduces the chance of encountering it as well as protects from other inadvertent user errors.

Current situation

Presently, upon opening entry from the 'entry-list' activity-window, the user is directly taken to an 'edit-mode' activity-window with edit-able fields. It is possible to inadvertently clobber previously entered values in the fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants