java.lang.Object | ||
↳ | android.support.v4.app.Fragment | |
↳ | android.support.v17.leanback.app.DetailsSupportFragment |
Known Direct Subclasses |
Wrapper fragment for leanback details screens.
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Returns the list of rows.
| |||||||||||
This method is deprecated.
Use
getOnItemViewClickedListener()
| |||||||||||
Returns the item Clicked listener.
| |||||||||||
Called to do initial creation of a fragment.
| |||||||||||
Called to have the fragment instantiate its user interface view.
| |||||||||||
Called when the Fragment is visible to the user.
| |||||||||||
Called immediately after
onCreateView(LayoutInflater, ViewGroup, Bundle)
has returned, but before any saved state has been restored in to the view.
| |||||||||||
Enables entrance transition.
| |||||||||||
Sets the list of rows for the fragment.
| |||||||||||
This method is deprecated.
Use
setOnItemViewClickedListener(OnItemViewClickedListener)
| |||||||||||
This method is deprecated.
Use
setOnItemViewSelectedListener(OnItemViewSelectedListener)
| |||||||||||
Sets an item Clicked listener.
| |||||||||||
Sets an item selection listener.
| |||||||||||
Sets the selected row position.
| |||||||||||
Sets the selected row position with smooth animation.
| |||||||||||
When fragment finishes loading data, it should call startEntranceTransition()
to execute the entrance transition.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Create entrance transition.
| |||||||||||
Callback when entrance transition is ended.
| |||||||||||
Callback when entrance transition is started.
| |||||||||||
Run entrance transition.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
android.support.v4.app.Fragment
| |||||||||||
From class
java.lang.Object
| |||||||||||
From interface
android.content.ComponentCallbacks
| |||||||||||
From interface
android.view.View.OnCreateContextMenuListener
|
Called to do initial creation of a fragment. This is called after
onAttach(Activity)
and before
onCreateView(LayoutInflater, ViewGroup, Bundle)
.
Note that this can be called while the fragment's activity is
still in the process of being created. As such, you can not rely
on things like the activity's content view hierarchy being initialized
at this point. If you want to do work once the activity itself is
created, see onActivityCreated(Bundle)
.
savedInstanceState | If the fragment is being re-created from a previous saved state, this is the state. |
---|
Called to have the fragment instantiate its user interface view.
This is optional, and non-graphical fragments can return null (which
is the default implementation). This will be called between
onCreate(Bundle)
and onActivityCreated(Bundle)
.
If you return a View from here, you will later be called in
onDestroyView()
when the view is being released.
inflater | The LayoutInflater object that can be used to inflate any views in the fragment, |
---|---|
container | If non-null, this is the parent view that the fragment's UI should be attached to. The fragment should not add the view itself, but this can be used to generate the LayoutParams of the view. |
savedInstanceState | If non-null, this fragment is being re-constructed from a previous saved state as given here. |
Called when the Fragment is visible to the user. This is generally
tied to Activity.onStart
of the containing
Activity's lifecycle.
Called immediately after onCreateView(LayoutInflater, ViewGroup, Bundle)
has returned, but before any saved state has been restored in to the view.
This gives subclasses a chance to initialize themselves once
they know their view hierarchy has been completely created. The fragment's
view hierarchy is not however attached to its parent at this point.
view | The View returned by onCreateView(LayoutInflater, ViewGroup, Bundle) . |
---|---|
savedInstanceState | If non-null, this fragment is being re-constructed from a previous saved state as given here. |
Enables entrance transition.
Entrance transition is the standard slide-in transition that shows rows of data in browse screen and details screen.
The method is ignored before LOLLIPOP (API21).
This method must be called in or
before onCreate(). Typically entrance transition should be enabled when savedInstance is
null so that fragment restored from instanceState does not run an extra entrance transition.
When the entrance transition is enabled, the fragment will make headers and content
hidden initially.
When data of rows are ready, app must call startEntranceTransition()
to kick off
the transition, otherwise the rows will be invisible forever.
It is similar to android:windowsEnterTransition and can be considered a late-executed android:windowsEnterTransition controlled by app. There are two reasons that app needs it:
Transition object is returned by createEntranceTransition(). Typically the app does not need override the default transition that browse and details provides.
This method is deprecated.
Use setOnItemViewClickedListener(OnItemViewClickedListener)
Sets an item Clicked listener.
This method is deprecated.
Use setOnItemViewSelectedListener(OnItemViewSelectedListener)
Sets an item selection listener.
Sets an item Clicked listener.
Sets an item selection listener.
Sets the selected row position.
Sets the selected row position with smooth animation.
When fragment finishes loading data, it should call startEntranceTransition() to execute the entrance transition. startEntranceTransition() will start transition only if both two conditions are satisfied:
If startEntranceTransition() is called before onViewCreated(), it will be pending and executed when view is created.
Create entrance transition. Subclass can override to load transition from resource or construct manually. Typically app does not need to override the default transition that browse and details provides.
Callback when entrance transition is ended.
Callback when entrance transition is started.
Run entrance transition. Subclass may use TransitionManager to perform go(Scene) or beginDelayedTransition(). App should not override the default implementation of browse and details fragment.