title: NumberPicker not graying out when disabled
body: <p>I believe I may have found a bug in the Android UI, but I'd like to make sure I'm not doing something flat out wrong. Here is a simplified version of the code I'm running that's causing the problem. This listener is set on a specific NumberPicker in my UI, and it properly disables / enables things, but if the user has changed the value of one of the other NumberPickers that it disables, it behaves a little bit oddly.</p>
  
  <p>It still properly disables the input, but it fails to grey the value out, making it look like it's still enabled. Is this intended? Am I doing something wrong?</p>
  
  <pre class="lang-java prettyprint-override"><code>NumberPicker.OnValueChangeListener diceChangeListener = new NumberPicker.OnValueChangeListener() {
      @Override
      public void onValueChange(NumberPicker picker, int oldVal, int newVal) {
          View parent = (View) picker.getParent();    
  
          if (newVal == 0) {
              ((NumberPicker) parent.findViewById(R.id.diceCountPicker1)).setEnabled(false);
          } else if (oldVal == 0) {
              ((NumberPicker) parent.findViewById(R.id.diceCountPicker1)).setEnabled(true);
          }
      }
  };
  </code></pre>
  
  <p>Let me know if there's a better way to do this, or if this is a legitimate bug. If it is a bug, is there a way to work around it?</p>
  
  <p>Edit: Here's the definition of diceCountPicker1 in the XML:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;NumberPicker
      android:id="@+id/diceCountPicker1"
      android:layout_width="48dp"
      android:layout_height="128dp"
      android:descendantFocusability="blocksDescendants"
      /&gt;
  </code></pre>
  
  <p>Edit 2:</p>
  
  <p>I have tested this in emulators, and confirmed that the problem doesn't exist before Jellybean (4.1). It works properly in ICS. That's... annoying. But I may be able to live with it for now. I'll leave this open for potential ways to work around the bug, but it looks to me like a real bug, and I doubt it can be fixed.</p>