Lines Matching refs:link
183 <p>The USB APIs are available in the package {@link android.hardware.usb}. The
184 central class is {@link android.hardware.usb.UsbManager}, which provides
187 {@link android.hardware.usb.UsbManager} and then query for the list of attached
189 {@link android.hardware.usb.UsbManager} also declares intent actions that the
196 <li>{@link android.hardware.usb.UsbDevice}, a class representing external
199 <li>{@link android.hardware.usb.UsbAccessory}, representing external hardware
202 <li>{@link android.hardware.usb.UsbInterface} and {@link
205 <li>{@link android.hardware.usb.UsbDeviceConnection} and {@link
208 <li>{@link android.hardware.usb.UsbConstants}, which provides constants for
255 <p>The MTP API is available in the {@link android.mtp} package and provides
259 <li>The {@link android.mtp.MtpDevice} encapsulates an MTP device that is
265 <li>{@link android.mtp.MtpDevice#getObjectHandles(int, int, int)
268 application can pass a handle to {@link android.mtp.MtpDevice#getObjectInfo(int)
270 <li>{@link android.mtp.MtpDevice#importFile(int, java.lang.String)
275 <li>{@link
278 <li>{@link android.mtp.MtpDevice#getThumbnail(int) getThumbnail()} returns
282 <li>{@link android.mtp.MtpStorageInfo} holds information about about a storage
287 <li>{@link android.mtp.MtpDeviceInfo} holds information about an MTP device
291 <li>{@link android.mtp.MtpObjectInfo} holds information about an object stored
296 <li>{@link android.mtp.MtpConstants} provides constants for declaring MTP file
311 <li>{@link android.view.MotionEvent#ACTION_SCROLL}, which describes the pointer
313 took place. In the MotionEvent, the value of the {@link
314 android.view.MotionEvent#AXIS_HSCROLL} and {@link
317 <li>{@link android.view.MotionEvent#ACTION_HOVER_MOVE}, reports the current
323 <p>To support joysticks and gamepads, the {@link android.view.InputDevice} class
326 <li>{@link android.view.InputDevice#SOURCE_CLASS_JOYSTICK} — the source
328 <li>{@link android.view.InputDevice#SOURCE_CLASS_BUTTON} — the source
330 <li>{@link android.view.InputDevice#SOURCE_GAMEPAD} — the source device
331 has gamepad buttons such as {@link android.view.KeyEvent#KEYCODE_BUTTON_A}
332 or {@link android.view.KeyEvent#KEYCODE_BUTTON_B}. Implies
333 {@link android.view.InputDevice#SOURCE_CLASS_BUTTON}</li>
334 <li>{@link android.view.InputDevice#SOURCE_JOYSTICK} — the source device
339 and trackballs, the platform now defines axis codes on {@link
340 android.view.MotionEvent}, similar to how it defines key codes on {@link
343 {@link android.view.MotionEvent#AXIS_HAT_X}, {@link
344 android.view.MotionEvent#AXIS_HAT_Y}, {@link
345 android.view.MotionEvent#AXIS_RTRIGGER}, {@link
346 android.view.MotionEvent#AXIS_ORIENTATION}, {@link
348 Existing {@link android.view.MotionEvent} axes are represented by {@link
349 android.view.MotionEvent#AXIS_X}, {@link android.view.MotionEvent#AXIS_Y},
350 {@link android.view.MotionEvent#AXIS_PRESSURE}, {@link
351 android.view.MotionEvent#AXIS_SIZE}, {@link
352 android.view.MotionEvent#AXIS_TOUCH_MAJOR}, {@link
353 android.view.MotionEvent#AXIS_TOUCH_MINOR}, {@link
354 android.view.MotionEvent#AXIS_TOOL_MAJOR}, {@link
355 android.view.MotionEvent#AXIS_TOOL_MINOR}, and {@link
358 <p>Additionally, {@link android.view.MotionEvent} defines a number of generic
362 interpretations, see the {@link android.view.MotionEvent} class documentation.
367 Applications should use {@link android.view.MotionEvent#getHistorySize()} to get
369 samples in order using {@link
372 sample using {@link android.view.MotionEvent#getAxisValue(int) getAxisValue()}.
376 instead of calling {@link android.view.MotionEvent#getAxisValue(int)
377 getAxisValue()}, applications can call {@link android.view.MotionEvent#getX(int)
378 getX()}. Axes that have built-in accessors include {@link
379 android.view.MotionEvent#AXIS_X}, {@link android.view.MotionEvent#AXIS_Y},
380 {@link android.view.MotionEvent#AXIS_PRESSURE}, {@link
381 android.view.MotionEvent#AXIS_SIZE}, {@link
382 android.view.MotionEvent#AXIS_TOUCH_MAJOR}, {@link
383 android.view.MotionEvent#AXIS_TOUCH_MINOR}, {@link
384 android.view.MotionEvent#AXIS_TOOL_MAJOR}, {@link
385 android.view.MotionEvent#AXIS_TOOL_MINOR}, and {@link
395 event, applications should use methods on the {@link android.view.InputDevice}
397 applications can use {@link android.view.InputDevice#getMotionRanges()
400 the {@link android.view.InputDevice.MotionRange} object specifies the source for
405 passing them to a {@link android.view.View} as "generic" motion events.
407 {@link android.view.View}s through a call to {@link
409 onGenericMotionEvent()}, rather than to {@link
414 event source class. {@link android.view.InputDevice#SOURCE_CLASS_POINTER} events
415 go to the {@link android.view.View} under the pointer, similar to how touch
416 events work. All others go to the currently focused {@link android.view.View}.
417 For example, this means a {@link android.view.View} must take focus in order to
419 level of Activity or Dialog by implementing {@link
438 <p>The RTP API is available in the {@link android.net.rtp} package. Classes
441 <li>{@link android.net.rtp.RtpStream}, the base class of streams that send and
443 <li>{@link android.net.rtp.AudioStream}, a subclass of {@link
445 <li>{@link android.net.rtp.AudioGroup}, a local audio hub for managing and
446 mixing the device speaker, microphone, and {@link android.net.rtp.AudioStream}.</li>
447 <li>{@link android.net.rtp.AudioCodec}, which holds a collection of codecs that
448 you define for an {@link android.net.rtp.AudioStream}.</li>
455 <li>{@link android.net.rtp.AudioStream} specifies a remote endpoint and consists
456 of network mapping and a configured {@link android.net.rtp.AudioCodec}.</li>
457 <li>{@link android.net.rtp.AudioGroup} represents the local endpoint for one
458 or more {@link android.net.rtp.AudioStream}s. The {@link android.net.rtp.AudioGroup} mixes
459 all the {@link android.net.rtp.AudioStream}s and optionally interacts with the device
465 {@link android.net.rtp.AudioGroup}.</p>
481 <code>resizeMode</code> attribute in the widget's {@link
508 <li>A new {@link android.view.ViewPropertyAnimator} class provides a
510 way for developers to animate select properties on {@link android.view.View} objects. The class
512 manage multiple simulataneous animations on a {@link android.view.View} object.
513 <p>Using the {@link android.view.ViewPropertyAnimator} is straightforward. To animate properties for
514 a {@link android.view.View}, call {@link android.view.View#animate()} to
515 construct a {@link android.view.ViewPropertyAnimator} object for that {@link android.view.View}. Us…
516 methods on the {@link android.view.ViewPropertyAnimator} to specify what property to
517 animate and how to animate it. For example, to fade the {@link android.view.View} to transparent,
518 call <code>alpha(0);</code>. The {@link android.view.ViewPropertyAnimator} object
519 handles the details of configuring the underlying {@link
526 <li>New {@link android.view.animation.Animation#getBackgroundColor()} and
527 {@link android.view.animation.Animation#setBackgroundColor(int)} methods let
534 <li>A new {@link android.animation.ValueAnimator#getAnimatedFraction()}
537 fraction used in the most recent frame update — from a {@link
547 <li>A new {@link android.view.View#buildLayer()} method lets an application
557 {@link android.view.View#setCameraDistance(float)} to set the distance from the
565 <li>A new {@link android.widget.DatePicker#getCalendarView()} method
566 lets you get a {@link android.widget.CalendarView} from a {@link
573 <li>A new {@link android.view.View.OnAttachStateChangeListener} lets you
575 callbacks when a View is attached or detached from its window. Use {@link
577 to add a listener and {@link
583 <li>A new method, {@link
588 <li>In the {@link android.app.Fragment} class, {@link
590 onInflate(attrs, savedInstanceState)} is deprecated. Please use {@link
597 <li>An {@link android.app.SearchManager#EXTRA_NEW_SEARCH} data key for {@link
606 resource attribute {@link android.R.attr#textCursorDrawable}.</li>
611 <li>A new convenience method, {@link
613 childIndex)}, is available in {@link android.widget.RemoteViews} subclasses, to
614 let you set the child displayed in {@link android.widget.ViewAnimator} and
615 {@link android.widget.AdapterViewAnimator} subclasses such as {@link
616 android.widget.AdapterViewFlipper}, {@link android.widget.StackView}, {@link
617 android.widget.ViewFlipper}, and {@link android.widget.ViewSwitcher}.</li>
622 <li>{@link android.view.KeyEvent} adds a range of generic keycodes to
624 {@link android.view.KeyEvent#isGamepadButton(int)} and several other
635 <li>{@link android.graphics.Bitmap#setHasAlpha(boolean)} lets an app indicate that
642 <li>{@link android.graphics.Bitmap#getByteCount()} gets a Bitmap's size in
644 <li>{@link android.graphics.Bitmap#getGenerationId()} lets an application find
646 <li>{@link android.graphics.Bitmap#sameAs(android.graphics.Bitmap)} determines
653 <li>{@link android.graphics.Camera} adds two new methods {@link
654 android.graphics.Camera#rotate(float, float, float) rotate()} and {@link
674 <p>To create a high-performance lock, pass {@link
676 call to {@link android.net.wifi.WifiManager#createWifiLock(int,
683 using new methods in {@link android.net.TrafficStats}. Applications can use the
692 the new methods {@link android.net.sip.SipProfile#getAuthUserName()
693 getAuthUserName()} and {@link
706 completion. To initiate this type of download, applications pass {@link
708 in the {@link
712 <li>A new method, {@link
722 adding the new extra {@link
723 android.app.DownloadManager#INTENT_EXTRAS_SORT_BY_SIZE} to an {@link
733 <ul><li>The {@link android.view.inputmethod.InputMethodSubtype} adds the
735 {@link
738 the method {@link
775 <li>{@link android.content.Intent#FLAG_INCLUDE_STOPPED_PACKAGES} —
778 <li>{@link android.content.Intent#FLAG_EXCLUDE_STOPPED_PACKAGES} —
787 <p>Note that the system adds {@link
792 {@link android.content.Intent#FLAG_INCLUDE_STOPPED_PACKAGES} flag to broadcast
805 <li>{@link android.content.Intent#ACTION_PACKAGE_FIRST_LAUNCH} — Sent to
810 <li>{@link android.content.Intent#ACTION_MY_PACKAGE_REPLACED} — Notifies
827 <li>A new {@link android.util.LruCache} class lets your applications benefit
830 memory footprint for the cached data.{@link android.util.LruCache} is a cache
839 <li>You can now get the native file descriptor int for a {@link
840 android.os.ParcelFileDescriptor} using either of the new methods {@link
841 android.os.ParcelFileDescriptor#getFd()} or {@link
858 <li>The {@link android.webkit.CookieManager} now supports cookies that use
860 <code>file:</code> URI scheme. You can use {@link
866 is enabled by calling {@link
874 method {@link
920 <li>{@link android.content.pm.PackageManager#FEATURE_USB_ACCESSORY
924 <li>{@link android.content.pm.PackageManager#FEATURE_USB_HOST