-
Notifications
You must be signed in to change notification settings - Fork 2
unsaved changes indicator in viewer #21
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
Comments
See also #22 |
Should I follow the behavior of MappingEditor._unsaved_modifications (set to True when arrays have been added/deleted + user made some changes AND clicked on Apply) or should I update the indicator as soon as the user changed the value of any cell (before user clicked on Apply)? Second question: MappingEditor._unsaved_modifications should be set to True as soon as the user changed the value of any cell (before user clicked on Apply)? |
Those two MUST be consistent, but yes _unsaved_modifications should ideally be True before apply. |
…s are detected. changed behavior of var unsaved_modifications (MappingEditor class): set to True as soon as data has been changed (before users click on Apply button)
…s are detected. changed behavior of var unsaved_modifications (MappingEditor class): set to True as soon as data has been changed (before users click on Apply button)
…s are detected. changed behavior of var unsaved_modifications (MappingEditor class): set to True as soon as data has been changed (before users click on Apply button)
…s are detected. changed behavior of var unsaved_modifications (MappingEditor class): set to True as soon as data has been changed (before users click on Apply button)
larray-project/larray#256
The text was updated successfully, but these errors were encountered: