Obsolete
Status Update
Comments
tn...@google.com <tn...@google.com>
[Deleted User] <[Deleted User]> #2
The iPhone Simulator has a nice UI for this. You hold down a key combo and you see
two finger spots on the emulator screen, mirrored around the center of the screen.
Drag away from the center to pinch open; drag toward the center to pinch closed.
two finger spots on the emulator screen, mirrored around the center of the screen.
Drag away from the center to pinch open; drag toward the center to pinch closed.
de...@gmail.com <de...@gmail.com> #3
That is nice, but that only handles the case of "pinch". It would be a good start,
and would handle probably the majority of common use cases, but there are certainly
very many ways I can move two fingers at once that don't even resemble a pinch. :)
and would handle probably the majority of common use cases, but there are certainly
very many ways I can move two fingers at once that don't even resemble a pinch. :)
Description
applicable)
Host OS: Linux
SDK tools version (available in the "About" section of the 'android' tool
UI): 22.6.1
Eclipse version: 4.3.2
ADT plug-in version: 22.6.1.v201403111859-1066720
Platform targeted by your project: Froyo and up
Version of the platform running in the emulator: n/a
We have a custom view class which looks a bit like this:
class CustomImageView extends ImageView {
public CustomImageView(Context context) {
this(context, null);
}
public CustomImageView(Context context, AttributeSet attrs) {
super(context, attrs);
}
Lint places an error (not a warning) on the 2nd constructor. The summary says
"This class should be public (com.my.class.CustomImageView)"
While the long-form description says,
"Activities, services, broadcast receivers etc. registered in
the manifest file must be "instantiatable" by the system,
which means that the class must be public, it must have an
empty public constructor, and if it's an inner class, it must
be a static inner class."
OK here are the problems we observe:
1. The error is placed on the 2nd constructor, but the summary line describes a problem with "this class".
2. The summary discusses entities that are registered in the manifest, and this is not applicable to a view.
3. It's unclear to us if anything is wrong at all; This code works fine on Froyo through current platforms. (For example, if the problem is that the class should have been public, this isn't actually true - the view inflater seems to find it with package visibility.)