Reworking the platform isn't an option...guess that leaves me with
some naming convention.
thanks,
mike
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To
And doesn't this also mean that there's an implicit requirement that I
prefix my methods with a tag to avoid future version name collisions?
If I have a method in my 1.6 app called MyView.doSomething(), and
MyView extends an Android class like TextView, and subsequent to 1.6,
Google adds a method
Does this truly mean that even if I compile to the 1.6 platform, if my
code implements a 2.1 callback method, that method will *never* be
invoked on 1.6 devices but *will* be invoked on 2.1 devices? Even
though I compiled to the 1.6 platform? That's crazy!
On Feb 12, 4:01 pm, Mike Collins
That would be very 'icky'... I hoped that the 'targetSdkVersion'
setting could prevent this.
On Feb 12, 7:20 pm, jasper jasper...@gmail.com wrote:
Does this truly mean that even if I compile to the 1.6 platform, if my
code implements a 2.1 callback method, that method will *never* be
invoked
4 matches
Mail list logo
