The deprecated warnings for attributes in XML in Lint is driven off of the
deprecation flags in R.attr:
http://developer.android.com/reference/android/R.attr.html#enabled
This constant is deprecated.
I guess we need to do some more filtering?
This is tracked in
issue
I'm working with 2.0 and in my xml layout, I changed the Enabled
property of a Button, only to see that that is Deprecated. Eclipse
property manager tells me (when I mouse over the property) :
Deprecated use state_enabled instead.
So sure I can set state_enabled in the xml layout, but how to do
I'm working with 2.0 and in my xml layout, I changed the Enabled
property of a Button, only to see that that is Deprecated. Eclipse
property manager tells me (when I mouse over the property) :
Deprecated use state_enabled instead.
So sure I can set state_enabled in the xml layout, but how to
This seems like a bug in Eclipse, View.setEnabled() is certainly not
deprecated. There might be a deprecated android:enabled attribute in
one of the XML tags supported by Android which could throw off the
Eclipse editor.
On Sun, Dec 6, 2009 at 6:38 PM, Paul idi...@gmail.com wrote:
I'm working
4 matches
Mail list logo