It's a big problem, isn't it? I found that the be...

# anko

[josephivie]

It's a big problem, isn't it? I found that the best way to handle it was actually to never require access to a view directly - instead, you use properties or events. It makes sense and works solidly for 90% of the cases.

For example, if you need the text that an EditText has, you would make the EditText stay in sync with a property using a TextWatcher. Then you can just read the property.

This works especially well if you are retaining state in your views through an object that exists between activity creations. The property that the view syncs with can just be in there. You never have to worry about state retention again.

I have a system that does all of this, but while it is open source, it's not well documented yet.