Home/ Questions/Q 8812893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T03:42:34+00:00

I have two view controllers which should work like described below: First view controller

  • 0

I have two view controllers which should work like described below:

First view controller displays a view which has a table in it. The table contains data which is constantly changing. I have a delegate method for reloading the data when a change occurs. So that is taken care of. When the user selects a row in the table I would like to display a second view which would also contain live data in text format (one UITextView which would constantly change).

I would like to allow the user to access view 1 while view 2 would still be monitoring and displaying live data and vice versa. While user is on view 2, view 1 should still be monitoring and displaying any changes in the table content.

I guess its like having two view controllers present at the same time and switching between them.

What is the easiest or the most standard way to accomplish this? I dont mind if its all done programatically.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s a little hard to tell what you’re asking here. First, views shouldn’t be processing data at all — they should only be displaying it. It sounds like what you’re describing is having a background process that updates to your second view. That process could certainly be running while your table is on screen, and when you switch to the second view, you can update it using this running process. Exactly how you would do this depends on the details of what you’re trying to do. So, I think we could help you better if you provide more context on what kind of process you want going on that updates your second view, and how choosing a row in your table affects that process.

    After Edit:

    You can certainly do what you want to do. I think the main thing is that you need to have a property (typed strong) in your first view controller that points to your second view controller, so that when you go back to the second controller a second time, it goes back to the same instance. Based on the selection from the table, you can start whatever process you need to populate your text view, and that process can keep running even after you go back to the table view, since that controller won’t get deallocated when it’s view goes off screen (due to the strong reference you have). You would just have to have some sort of if clause in your second view controller to know whether the user has selected the same row again, and if so, just show the updated text view, rather than starting a new process.

    That’s about as specific as I can be without more detail from you.

    • 0