You can set a tag for the view, and then use viewWithTag to search when needed - this is not recommended, it is too obscure, error-prone, and the search efficiency is not high.
If you need to access a view in the controller, you should connect it out and save a reference in the controller - normally this is what you should do.
According to your needs, it is not appropriate to let view2 be the proxy of view1. View should only be responsible for displaying and accepting user operations. What subsequent actions are required after the operation is completed should be the responsibility of the controller, or you can use MVVM, view Bound to the viewModel, when the user performs any operation, the corresponding viewModel is updated, and the view on the other side monitors the changes in the viewModel and responds accordingly.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
You can set a tag for the view, and then use viewWithTag to search when needed - this is not recommended, it is too obscure, error-prone, and the search efficiency is not high.
If you need to access a view in the controller, you should connect it out and save a reference in the controller - normally this is what you should do.
According to your needs, it is not appropriate to let view2 be the proxy of view1. View should only be responsible for displaying and accepting user operations. What subsequent actions are required after the operation is completed should be the responsibility of the controller, or you can use MVVM, view Bound to the viewModel, when the user performs any operation, the corresponding viewModel is updated, and the view on the other side monitors the changes in the viewModel and responds accordingly.