commit | 99e222d5b14544bbb89d402eb704829c642f8abf | [log] [tgz] |
---|---|---|
author | Dake Gu <dake@google.com> | Thu Oct 26 11:21:12 2017 -0700 |
committer | Dake Gu <dake@google.com> | Thu Oct 26 17:56:28 2017 -0700 |
tree | 49b3154eea765338a74d1085b07d582a6c0d9690 | |
parent | 75b4b9d334e884f40b70039b9df8f5c840179476 [diff] |
leanback: fix duplicated fragment in BrowseFragment.setAdapter() When calling BrowseFragment.setAdapter() with a list of rows, a fragment will be created, then later initial row selection will create another copy of fragment. This also breaks slide-in entrance transition that was launched on first fragment and immediately was wiped off by second fragment replacement. The fix removes replaceMainFragment() call from setAdapter(). Also some minor fix to allow setAdapter(null). Currently sample app call setAdapter() with empty list first. So it does not show the problem of duplicated fragment. This fix enables sample code to call setAdapter() with loaded data which is very important in restoring view state. Gridview needs to get list of data in first layout pass in order to restore focus index and children states. For example if there is only 1 item in the first layout pass after restoring, GridView is unable to restore focus index to 3. Added lots of BrowseFragment tests for checking savedInstance gets restored properly. Fixed generatev4.py script for demo app after new directory sturcture. Bug: 68273047 Test: browseFragmentSetNullAdapter browseFragmentRestore mixedBrowseFragmentRestoreToListRow mixedBrowseFragmentRestoreToSampleRowsFragmentHideFastLane mixedBrowseFragmentRestoreToSampleRowsFragmentShowFastLane mixedBrowseFragmentRestoreToSampleFragmentHideFastLane mixedBrowseFragmentRestoreToSampleFragmentShowFastLane Manual test, turn on "dont keep activity", start BrowseActivity, click card to open DetailsActivity, hit BACK, BrowseActivity is recreated, focus is restored to exact same row and item. Change-Id: I2e2a703b142e6f9573ee961042ed92792bf8c9a5
We are not currently accepting new modules, features, or behavior changes.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
Follow the “Downloading the Source” guide to install and set up repo
tool, but instead of running the listed repo
commands to initialize the repository, run the folowing:
repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master
Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
Open path/to/checkout/frameworks/support/
in Android Studio. Now you're ready edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full support library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
Run FooBarTest
Run android.support.foobar
Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ...
and choosing the desired application.
cd path/to/checkout/frameworks/support/ repo start my_branch_name . (make needed modifications) git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?