I'm new to iPhone development and struggling to find what I think is neat in this issue.
I have a user interface where a summary of the recording data is displayed in a table inside the navigation controller. When the user presses the accessory button for a line, a new view is displayed on the navigation controller, displaying a view in which the user can edit the data in the corresponding record. After that, the edit window opens from the window of the navigation controller stack and the user returns to the table view.
My problem is that when the user returns to the table view, the table still shows the state of the data before the record has been edited. Therefore, I have to reload the table data to show the changes.
It seems impossible to reload the table data before it is displayed, since the call only updates the displayed records. Rebooting after displaying the table leads to the fact that the old data changes before the eyes of the user, which I am not too happy.
It seems to me that this is a pretty normal thing to do in an iPhone app.
Can anyone suggest a best practice approach for this? I feel something is missing.
Cheers - Steve.