What's the need to call DataBindingUtil.setContentView() when using Data Binding Library?

Viewed 7502

I am learning to use Data Binding Library. I came to know that it removes the need to call findViewById() manually and makes the code more robust and readable.

To understand the use, I did the following:

  1. made a temp_layout.xml which contains 2 text views with ids 'tv1' and 'tv2'

  2. added the <layout> tag as root

  3. clicked on 'build project'

Now I found that a new 'TempLayoutBinding' class was available which contained the variables 'tv1' and 'tv2'.

My question is that, even when I already specified the <layout> tag in the temp_layout.xml, why do I still need to call mBinding = DataBindingUtil.setContentView(...)? What specifically does it do?

2 Answers
Related