commit | 9d375c31c81da95b8fb82371cbd6dfe7563aa8bb | [log] [tgz] |
---|---|---|
author | Andrei Stingaceanu <stg@google.com> | Tue May 23 16:11:19 2017 +0100 |
committer | Andrei Stingaceanu <stg@google.com> | Wed May 24 10:38:16 2017 +0100 |
tree | 19117483b70c6c297a27ea2949a109ffbbd1054f | |
parent | 62142c0d82137f8a3e0c9e95233bdeb203f72826 [diff] |
AutoSize TextView - support - correct pixel transformations When configuring a TextView to auto-size via min/max/granularity do the calculations in float pixels and only convert to int (via rounding, see TypedArray#getDimensionPixelSize) to produce the final text size values to be used by the auto-size algorithm. This is because the previous version where the values were initially directly converted to pixels and only after used in calculations was losing precision and was not consistent with how we deal with preset configuration (and the developer expectations). Practically textView1.setAutoSizeTextTypeUniformWithConfiguration(10, 20, 2, TypedValue.COMPLEX_UNIT_SP) and textView2.setAutoSizeTextTypeUniformWithPresetSizes( new int[] {10, 12, 14, 16, 18, 20}, TypedValue.COMPLEX_UNIT_SP); produce exactly the same values in pixels to choose from when auto-sizing (on any device) => (TextView#getAutoSizeTextAvailableSizes()) Bug: 38185233 Bug: 37265610 Test: ./gradlew support-appcompat-v7:connectedCheck --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=android.support.v7.widget.AppCompatTextViewAutoSizeTest#testAutoSizeUniform_equivalentConfigurations Change-Id: Ie1de4c3a8caad424f1588de814063d7d46d01132
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)?