Side effects of calling Activity.setContentView() twice in a row
-
24-10-2019 - |
Question
In my app I needed to call findViewbyId()
from both onCreate()
and from WebChromeClient.onCompletion()
. To avoid findViewbyId()
returning null I resorted to calling Activity.setContentView(int viewResID)
before calling findViewbyId()
.
It works, but now I am wondering whether I may have created a "time-bomb" in my code down the road.
Are there any caveats that I need to keep in mind when doing something like this?
Solution
There is no problem in doing so. You have to reinitialize references (every findViewById needs to be called again) and it might be troublesome if you do it A LOT of times, but it is not a time bomb at all.
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow