| commit | f468c07ab53ab9531f927604d347323ab8afad1a | [log] [tgz] |
|---|---|---|
| author | Andrei Stingaceanu <stg@google.com> | Mon Jun 05 15:15:26 2017 +0100 |
| committer | Andrei Stingaceanu <stg@google.com> | Fri Jun 09 13:30:07 2017 +0100 |
| tree | df628ac051c85b5aceecbf9686b58fb7f7f785e6 | |
| parent | 912315a7c2a255b6a0ee327704ee82ed0922b8ea [diff] |
AutoSize TextView - support - major fixes
* splits the auto-size setup part from the execution
function:
** in TextView CTOR we only setup and we leave the
actual auto-sizing execution to happen in the
view||text layout phase
** encapsulated the conditions needed to start
applying auto-size in the execution function
* calls execution autoSizeText() when the text changes
=> this makes sure that auto-size will be
performed even if a view layout is not requested,
but only a text layout
* fixes the calculation of the sizes available for
auto-size when configured via granularity
* introduces test to verify that the text size gets
scaled up and down for an auto-sizing TextView when
the text itself is changed
* fixes flakiness of some auto-size tests on different
devices
* for API > 18 adds check to verify that we do not request
the layout while the view hierarchy is undergoing a
layout pass, but only forceLayout which does not call
requestLayout() or forceLayout() on the parent.
* cleanup - removed unused methods
Bug: 62050646
Bug: 38409622
Bug: 38440435
Bug: 62109627
Bug: 62107864
Test: ./gradlew support-appcompat-v7:connectedCheck --info --daemon
-Pandroid.testInstrumentationRunnerArguments.class=android.support.v7.widget.AppCompatTextViewTest
Test: ./gradlew support-appcompat-v7:connectedCheck --info --daemon
-Pandroid.testInstrumentationRunnerArguments.class=android.support.v7.widget.AppCompatTextViewAutoSizeTest
Change-Id: I276786d9706392b0bbef9bf2b3869b432760e3cc
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 FooBarTestRun android.support.foobarSupport 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)?