Status Update
Comments
gr...@google.com <gr...@google.com> #2
gr...@google.com <gr...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-main
Author: leo huang <
Link:
Add VideoCapture.getSelectedQuality() API
Expand for full commit details
Add VideoCapture.getSelectedQuality() API
This API allows retrieving the selected Quality for a VideoCapture instance based on the provided QualitySelector.
The getSelectedQuality() method returns a value only when the VideoCapture is bound to a lifecycle.
This API was requested by both JCA and 3rd-party developers.
Relnote: "Add VideoCapture.getSelectedQuality() to know the selected Quality based on the QualitySelector."
Bug: 204288986
Test: VideoCaptureTest
Change-Id: I7050868dea1f1654386c991d441c25af2e3f1fe4
Files:
- M
camera/camera-core/src/main/java/androidx/camera/core/impl/StreamSpec.java
- A
camera/camera-core/src/main/java/androidx/camera/core/streamsharing/PreferredChildSize.kt
- M
camera/camera-core/src/main/java/androidx/camera/core/streamsharing/ResolutionsMerger.java
- M
camera/camera-core/src/main/java/androidx/camera/core/streamsharing/StreamSharing.java
- M
camera/camera-core/src/main/java/androidx/camera/core/streamsharing/VirtualCameraAdapter.java
- M
camera/camera-core/src/test/java/androidx/camera/core/streamsharing/ResolutionsMergerTest.kt
- M
camera/camera-core/src/test/java/androidx/camera/core/streamsharing/VirtualCameraAdapterTest.kt
- M
camera/camera-video/api/current.txt
- M
camera/camera-video/api/restricted_current.txt
- M
camera/camera-video/src/main/java/androidx/camera/video/VideoCapture.java
- M
camera/camera-video/src/test/java/androidx/camera/video/VideoCaptureTest.kt
Hash: f24822959fa0cc4dc6b1c5400b1d4ab46fb2c18b
Date: Mon Dec 23 15:29:59 2024
se...@google.com <se...@google.com>
se...@google.com <se...@google.com> #4
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.camera:camera-core:1.5.0-alpha05
androidx.camera:camera-video:1.5.0-alpha05
se...@google.com <se...@google.com> #5
private val fontWeights = listOf(100, 200, 300, 400)
private val fonts = listOf(
"Azeret" to R.font.azeret_mono,
"Roboto Mono" to R.font.roboto_mono,
)
@OptIn(ExperimentalTextApi::class)
private val fontFamilies = fonts.map { (_, resId) ->
FontFamily(
fontWeights.map { weight ->
Font(
resId = resId,
weight = FontWeight(weight),
variationSettings = FontVariation.Settings(FontVariation.weight(weight))
)
}
)
}
@Composable
fun Demo() {
Column {
FullListRepro()
// FullListOK()
}
}
@Composable
fun FullListRepro() {
Column {
fontWeights.forEach { weight ->
fonts.forEachIndexed { i, (familyName, _) ->
val fontFamily = fontFamilies[i]
val style = TextStyle(
fontFamily = fontFamily,
fontWeight = FontWeight(weight),
fontSize = 40.sp
)
BasicText("$weight $familyName", style=style)
}
}
}
}
@Composable
fun FullListOK() {
Column {
fonts.forEachIndexed { i, (familyName, _) ->
fontWeights.forEach { weight ->
val fontFamily = fontFamilies[i]
val style = TextStyle(
fontFamily = fontFamily,
fontWeight = FontWeight(weight),
fontSize = 40.sp
)
BasicText("$weight $familyName", style=style)
}
}
}
}
OK composable is fine, but if you switch the order you see the incorrect behavior coming from resource font loading.
se...@google.com <se...@google.com>
mo...@gmail.com <mo...@gmail.com> #6
When setting the fontWeight, either in the TextStyle, or in the TextField, ... 100-300 shows same weight, 400-600 shows same weight etc ...
When setting it as FontVariation.Setting it is working correctly ...
Is this need to explicitly mention for variable fonts ?
se...@google.com <se...@google.com> #7
That issue is a little bit different
We don't do any draw time istantiation of font axes.
You can get the behavior you expect by defining multiple instances of the font. One for each font weight that you want to support. You can put them in a FontFamily, and then matching is done by (FontWeight, Style)
se...@google.com <se...@google.com>
ap...@google.com <ap...@google.com> #8
Project: platform/frameworks/support
Branch: androidx-main
Author: Sean McQuillan <
Link:
Don't allow Paint to cache variation settings of resource fonts
Expand for full commit details
Don't allow Paint to cache variation settings of resource fonts
Prev: Loading two resource fonts with the same variation settings would cause the variation settings to not be applied to the second font.
New: Paint cache is invalidated during font load path.
Fixes: b/372044241
Test: manual of variable font demo
Relnote: "Resource fonts with the same variation settings will now avoid over-caching causing the incorrect variation settings to be applied."
Change-Id: If3dff4ea44e33b1ed80bc7fb5057923a088f1678
Files:
- M
compose/ui/ui-text/src/androidMain/kotlin/androidx/compose/ui/text/font/PlatformTypefaces.android.kt
Hash: 8ad5f10469c5a044be4fd8a90fc19c5614f61734
Date: Tue Oct 15 16:25:26 2024
pr...@google.com <pr...@google.com> #9
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.ui:ui-text:1.8.0-alpha08
androidx.compose.ui:ui-text-android:1.8.0-alpha08
androidx.compose.ui:ui-text-jvmstubs:1.8.0-alpha08
androidx.compose.ui:ui-text-linuxx64stubs:1.8.0-alpha08
Description
- Jetpack Compose component used: FontVariation
- Android Studio Build: Build #AI-241.18034.62.2412.12266719, built on August 23, 2024
- Kotlin version: 1.9.0, 2.0.20
- Devices/Android versions reproduced on: Pixel 8 Pro API 35 emulator
- Keyboard (i.e. Gboard, Samsung, etc): Gboard
- Sample project to trigger the issue:
A screen recording was attached.
Description of the minimal example:
I'm using two variable fonts: Azeret Mono and Roboto Mono.
For each font I created a map containing 4 different font weights(100, 200, 300, 400). I'm persisting this weight info along with the font index in a DataStore.
Using a slider and a menu I'm changing the style of a Text.
Observed behavior:
- negative case:
When I open the app and change the font from Azeret(200) to Roboto(200) the displayed style is Roboto(400) instead. Similar behavior can be observed with other configurations too.
- positive case:
When I open the app and play around with the slider first and then change the font, everything looks fine.