title: Is the textViewResourceId argument always necessary?
body: <p>While writing my own adapter that extends the <strong>ArrayAdapter</strong> class, I came across the different constructors available and I noticed they all require a <em>textViewResourceId</em> parameter.  So initially, I decided that I would feed my custom adapter class <strong>android.R.id.text1</strong>:</p>
  
  <pre><code>MyAdapter adapter = new MyAdapter(this, R.layout.myRow, android.R.id.text1);
  </code></pre>
  
  <p>However, later on during my development, I decided to override <strong>getView</strong> method where I would</p>
  
  <pre><code>TextView label = (TextView) myRow.findViewById(android.R.id.text1);
  label.setText("Position #" + position);
  </code></pre>
  
  <p>Which worked fine.  But then this question came to mind: if I'm doing the logic for how to display the row, is it really necessary to provide a <em>textViewResourceId</em> to the constructor when I initiate my custom adapter? Or is it the case that when you override <strong>getView</strong>, that parameter is no longer necessary? If my thinking is correct, what is the common practice for instantiating the adapter knowing that you will be overriding the display behavior anyways?</p>