Window

The default features enabled

Flag for enabling the Action Bar. This is enabled by default for some devices. The Action Bar replaces the title bar and provides an alternate location for an on-screen menu button on some devices.

Flag for requesting an Action Bar that overlays window content. Normally an Action Bar will sit in the space above window content, but if this feature is requested along with FEATURE_ACTION_BAR it will be layered over the window content itself. This is useful if you would like your app to have more control over how the Action Bar is displayed, such as letting application content scroll beneath an Action Bar with a transparent background or otherwise displaying a transparent/translucent Action Bar over application content.

This mode is especially useful with View.SYSTEM_UI_FLAG_FULLSCREEN, which allows you to seamlessly hide the action bar in conjunction with other screen decorations.

As of JELLY_BEAN, when an ActionBar is in this mode it will adjust the insets provided to View.fitSystemWindows(Rect) to include the content covered by the action bar, so you can do layout within that space.

Flag for specifying the behavior of action modes when an Action Bar is not present. If overlay is enabled, the action mode UI will be allowed to cover existing window content.

Flag for the context menu. This is enabled by default.

Flag for custom title. You cannot combine this feature with other title features.

Flag for indeterminate progress

Flag for having an icon on the left side of the title bar

Flag for the "no title" feature, turning off the title at the top of the screen.

Flag for the "options panel" feature. This is enabled by default.

Flag for the progress indicator feature

Flag for having an icon on the right side of the title bar

The ID that the main layout in the XML layout file should have.

Ending value for the (primary) progress

Flag for setting the progress bar's indeterminate mode off

Flag for setting the progress bar's indeterminate mode on

Highest possible value for the secondary progress

Lowest possible value for the secondary progress

Starting value for the (primary) progress

Flag for setting the progress bar's visibility to GONE

Flag for setting the progress bar's visibility to VISIBLE

Variation on setContentView(View, android.view.ViewGroup.LayoutParams) to add an additional content view to the screen. Added after any existing ones in the screen -- existing views are NOT removed.

Convenience function to set the flag bits as specified in flags, as per setFlags(int, int).

Convenience function to clear the flag bits as specified in flags, as per setFlags(int, int).

Finds a view that was identified by the id attribute from the XML that was processed in onCreate(Bundle). This will implicitly call getDecorView() for you, with all of the associated side-effects.

Retrieve the current window attributes associated with this panel.

Return the current Callback interface for this window.

Return the container for this Window.

Return the Context this window policy is running in, for retrieving resources and other information.

Return the view in this Window that currently has focus, or null if there are none. Note that this does not look in any containing Window.

Retrieve the top-level window decor view (containing the standard window frame/decorations and the client's content inside of that), which can be added as a window to the window manager.

Note that calling this function for the first time "locks in" various window characteristics as described in setContentView(View, android.view.ViewGroup.LayoutParams).

Quick access to the LayoutInflater instance that this Window retrieved from its Context.

Return the window manager allowing this Window to display its own windows.

Return the Window attributes from this window's theme.

Query for the availability of a certain feature.

Inject an event to window locally.

Return whether this window is being displayed with a floating style (based on the windowIsFloating attribute in the style/theme).

Is a keypress one of the defined shortcut keys for this window.

Should be called when the configuration is changed.

Retrieve the current decor view, but only if it has already been created; otherwise returns null.

Enable extended screen features. This must be called before setContentView(). May be called as many times as desired as long as it is before setContentView(). If not called, no extended features will be available. You can not turn off a feature once it is requested. You canot use other title features with FEATURE_CUSTOM_TITLE.

Specify custom window attributes. PLEASE NOTE: the layout params you give here should generally be from values previously retrieved with getAttributes(); you probably do not want to blindly create and apply your own, since this will blow away any values set by the framework that you are not interested in.

Change the background of this window to a custom Drawable. Setting the background to null will make the window be opaque. To make the window transparent, you can use an empty drawable (for instance a ColorDrawable with the color 0 or the system drawable android:drawable/empty.)

Change the background of this window to a Drawable resource. Setting the background to null will make the window be opaque. To make the window transparent, you can use an empty drawable (for instance a ColorDrawable with the color 0 or the system drawable android:drawable/empty.)

Set the Callback interface for this window, used to intercept key events and other dynamic operations in the window.

Set the container for this window. If not set, the DecorWindow operates as a top-level window; otherwise, it negotiates with the container to display itself appropriately.

Convenience for setContentView(View, android.view.ViewGroup.LayoutParams) to set the screen content from a layout resource. The resource will be inflated, adding all top-level views to the screen.

Convenience for setContentView(View, android.view.ViewGroup.LayoutParams) set the screen content to an explicit view. This view is placed directly into the screen's view hierarchy. It can itself be a complex view hierarhcy.

Set the screen content to an explicit view. This view is placed directly into the screen's view hierarchy. It can itself be a complex view hierarchy.

Note that calling this function "locks in" various characteristics of the window that can not, from this point forward, be changed: the features that have been requested with requestFeature(int), and certain window flags as described in setFlags(int, int).

Set the amount of dim behind the window when using FLAG_DIM_BEHIND. This overrides the default dim amount of that is selected by the Window based on its theme.

Set an explicit Drawable value for feature of this window. You must have called requestFeature(featureId) before calling this function.

Set a custom alpha value for the given drawale feature, controlling how much the background is visible through it.

Set the value for a drawable feature of this window, from a resource identifier. You must have called requestFeauture(featureId) before calling this function.

Set the value for a drawable feature of this window, from a URI. You must have called requestFeature(featureId) before calling this function.

The only URI currently supported is "content:", specifying an image in a content provider.

Set the integer value for a feature. The range of the value depends on the feature being set. For FEATURE_PROGRESSS, it should go from 0 to 10000. At 10000 the progress is complete and the indicator hidden.

Set the flags of the window, as per the WindowManager.LayoutParams flags.

Note that some flags must be set before the window decoration is created (by the first call to setContentView(View, android.view.ViewGroup.LayoutParams) or getDecorView(): FLAG_LAYOUT_IN_SCREEN and FLAG_LAYOUT_INSET_DECOR. These will be set for you based on the windowIsFloating attribute.

Set the format of window, as per the PixelFormat types. This overrides the default format that is selected by the Window based on its window decorations.

Set the gravity of the window, as per the Gravity constants. This controls how the window manager is positioned in the overall window; it is only useful when using WRAP_CONTENT for the layout width or height.

Set the primary icon for this window.

Set the width and height layout parameters of the window. The default for both of these is MATCH_PARENT; you can change them to WRAP_CONTENT or an absolute value to make a window that is not full-screen.

Set focus locally. The window should have the FLAG_LOCAL_FOCUS_MODE flag set already.

Set the logo for this window. A logo is often shown in place of an icon but is generally wider and communicates window title information as well.

Specify an explicit soft input mode to use for the window, as per WindowManager.LayoutParams.softInputMode. Providing anything besides "unspecified" here will override the input mode the window would normally retrieve from its theme.

Set the type of the window, as per the WindowManager.LayoutParams types.

Set extra options that will influence the UI for this window.

Set extra options that will influence the UI for this window. Only the bits filtered by mask will be modified.

Specify custom animations to use for the window, as per WindowManager.LayoutParams.windowAnimations. Providing anything besides 0 here will override the animations the window would normally retrieve from its theme.

Set the window manager for use by this Window to, for example, display panels. This is not used for displaying the Window itself -- that must be done by the client.

Set the window manager for use by this Window to, for example, display panels. This is not used for displaying the Window itself -- that must be done by the client.

Used by custom windows, such as Dialog, to pass the generic motion event further down the view hierarchy. Application developers should not need to implement or call this.

Used by custom windows, such as Dialog, to pass the key press event further down the view hierarchy. Application developers should not need to implement or call this.

Used by custom windows, such as Dialog, to pass the key shortcut press event further down the view hierarchy. Application developers should not need to implement or call this.

Used by custom windows, such as Dialog, to pass the touch screen event further down the view hierarchy. Application developers should not need to implement or call this.

Used by custom windows, such as Dialog, to pass the trackball event further down the view hierarchy. Application developers should not need to implement or call this.

Take ownership of this window's InputQueue. The window will no longer read and dispatch input events from the queue; it is your responsibility to do so.

Request that key events come to this activity. Use this if your activity has no views with focus, but the activity still wants a chance to process key events.

Take ownership of this window's surface. The window's view hierarchy will no longer draw into the surface, though it will otherwise continue to operate (such as for receiving input events). The given SurfaceHolder callback will be used to tell you about state changes to the surface.

Return the feature bits that are enabled. This is the set of features that were given to requestFeature(), and are being handled by this Window itself or its container. That is, it is the set of requested features that you can actually use.

To do: add a public version of this API that allows you to check for features by their feature ID.

Return the window flags that have been explicitly set by the client, so will not be modified by getDecorView().

Return the feature bits that are being implemented by this Window. This is the set of features that were given to requestFeature(), and are being handled by only this Window itself, not by its containers.

Has the app specified their own soft input mode?

Set the default format of window, as per the PixelFormat types. This is the format that will be used unless the client specifies in explicit format with setFormat();