You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The view behind the modal should refresh with the database changes on modal "save and close". A fireEvent/eventListener should do the trick. However...
At the moment an alert is set to trigger when this event fires. This alert will fire more than once on subsequent edits to a transect, when it should only always fire once.
Understanding and preventing this should make "tableView behind modal refresh automatically" possible.
The text was updated successfully, but these errors were encountered:
More detail: the alert only fires more than once when going back a screen and re-entering the transects screen. So it must be that when using the top-left button to go back to a previous screen, the current screen is not actually closed, but put in a suspended state. Navigating forward to that view again opens another copy of it. Seems prone to memory misuse.
Moved the code that populated the tableView into a function. When closing the modal view, fired a global event that calls the populateTable function. This solved the issue with the table not updating.
The view behind the modal should refresh with the database changes on modal "save and close". A fireEvent/eventListener should do the trick. However...
At the moment an alert is set to trigger when this event fires. This alert will fire more than once on subsequent edits to a transect, when it should only always fire once.
Understanding and preventing this should make "tableView behind modal refresh automatically" possible.
The text was updated successfully, but these errors were encountered: