Tgo1014
06/14/2022, 6:54 PMJohn Nichol
06/15/2022, 6:08 PMScalingLazyColumn
to be visible in Android Studio Previews.Yingding Wang
06/16/2022, 11:10 AMYingding Wang
06/16/2022, 9:41 PMWearNavScaffold
of horologist. I used a scalingLazyColumnComposable
to show a menu and default time text. Wenn I swipe back to the menu screen, the time text is gone. Is it desired behaviour?
My navi graph codeDaniel Quantil
06/17/2022, 5:27 AMZoltan Demant
06/17/2022, 5:40 AMrememberRipple()
in a shared module. Is it OK to bring in material as implementation
(not api
) even though the module is eventually consumed by both phone & wear variants that make use of material/material-wear?
Docs advice against mixing these up, but afaik thats just to ensure that you dont make use of the wrong MaterialTheme
(etc); material-wear itself depends on material?yschimke
06/17/2022, 4:09 PMTgo1014
06/17/2022, 6:59 PMsetFreshnessIntervalMillis
when overriding onTileRequest
. I'm using the Horologist's CoroutinesTileService
where onTileRequest
is final so I can't change when it should refresh. Is there some option for it?bod
06/18/2022, 7:28 PMyschimke
06/20/2022, 8:38 AMJohn Nichol
06/22/2022, 5:49 PMjames
06/24/2022, 6:29 AManimateItemPlacement()
for ScalingLazyColumn
?bod
06/25/2022, 6:28 AMJohn Nichol
06/30/2022, 6:14 AMyschimke
07/01/2022, 1:57 PMyschimke
07/03/2022, 9:10 AMYingding Wang
07/03/2022, 12:10 PMscrollableColumn
modifier doesn’t seem to register the rotation of GW4 bezel. Is this still the way to do it with onRotaryScrollEvent
modifier (https://stackoverflow.com/questions/70060650/how-to-implement-positionindicator-for-bezel-galaxy-watch-4-classic-wear-os-3) ?yschimke
07/04/2022, 3:31 PMZoltan Demant
07/11/2022, 11:53 AM"cannot access file, it is used by another process"
errors after adopting compose for my phone app; I saw that IntelliJ addressed it in one of their latter releases, and after it got merged into Android Studio I havent ran into it again.
Unfortunately, the same thing seems to repeat itself now that Im actively working on a wear specific app. Has anyone else ran into this? Any insights?Zoltan Demant
07/14/2022, 9:15 AMTextStyle
provided through LocalTextStyle
, which I wouldnt have any access to. At the same time, I have my own design system (which leans on material); components with text all make use of my custom Text composable as well (and provide the appropiate style). The material/material-wear text composables look very similar to me, is there anything else I should keep in mind before doing this?bod
07/14/2022, 3:59 PMScalingLazyColumn
with a TimeText
as the first item, so it scrolls with the rest of the contents? (Like the system settings).
The samples I can find seem to make it fade away in complicated ways 🙂
And if I naively put a TimeText as the first item in my list, it takes the whole screen height 🤔bod
07/14/2022, 4:44 PMToggleChip
with ToggleChipDefaults.switchIcon
, correct? Is there a way to animate the toggle switch?bod
07/16/2022, 9:23 PMProsper Ekwerike
07/20/2022, 9:20 AMlouiscad
07/24/2022, 4:44 PMYingding Wang
07/25/2022, 5:37 PMcom.google.android.support:wearable
to the androidx.wear
libs? There is a mapping for the android.support.wear
lib (https://developer.android.com/jetpack/androidx/migrate/class-mappings), but I haven’t found one for com.google.android.support:wearable
sofar, which contains Watchface, Complication and so on, the kotlin one might be https://developer.android.com/jetpack/androidx/releases/wear-watchface, and it feels almost impossible to just switch the libs, but more like to rewrite everything new. I would really appreciate any hints of how to do that gradually, instead of a big bang.John Nichol
07/27/2022, 5:15 PMenighma
08/02/2022, 5:53 PMyschimke
08/05/2022, 7:52 AMYingding Wang
08/05/2022, 10:02 AMval state: ScalingLazyListState = rememberScalingLazyListState()
Scaffold (
vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
ScalingLazyColumn (
modifier = Modifier.fillMaxSize(),
verticalArrangement = Arrangement.Center,
state = state,
anchorType = ScalingLazyListAnchorType.ItemCenter,
) {...
After I set the ScalingLazyListState(), and autoCentering both to (0, 0), the first element is shown correctly.
val state: ScalingLazyListState = rememberScalingLazyListState(
initialCenterItemIndex = 0,
initialCenterItemScrollOffset = 0
)
Scaffold (
vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
ScalingLazyColumn (
modifier = Modifier.fillMaxSize(),
verticalArrangement = Arrangement.Center,
state = state,
anchorType = ScalingLazyListAnchorType.ItemCenter,
autoCentering = AutoCenteringParams(itemIndex = 0, itemOffset = 0)
) {...
And set to (1, 0) as the both defaults are, doesn’t work. (0, 0) seems to be the only working combi. I think this issue was also present in horologist (https://github.com/google/horologist/issues/245).
Any thoughts on this are appreciated.
Update: It is worth to mention that my items are two full screen elements. After I scrolled the screen, the code behaved like I had set (0, 0).
item {
Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
Text(text = "Hello World!")
}
}
Yingding Wang
08/05/2022, 10:02 AMval state: ScalingLazyListState = rememberScalingLazyListState()
Scaffold (
vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
ScalingLazyColumn (
modifier = Modifier.fillMaxSize(),
verticalArrangement = Arrangement.Center,
state = state,
anchorType = ScalingLazyListAnchorType.ItemCenter,
) {...
After I set the ScalingLazyListState(), and autoCentering both to (0, 0), the first element is shown correctly.
val state: ScalingLazyListState = rememberScalingLazyListState(
initialCenterItemIndex = 0,
initialCenterItemScrollOffset = 0
)
Scaffold (
vignette = { Vignette(vignettePosition = VignettePosition.TopAndBottom) },
positionIndicator = { PositionIndicator(scalingLazyListState = state) }
) {
ScalingLazyColumn (
modifier = Modifier.fillMaxSize(),
verticalArrangement = Arrangement.Center,
state = state,
anchorType = ScalingLazyListAnchorType.ItemCenter,
autoCentering = AutoCenteringParams(itemIndex = 0, itemOffset = 0)
) {...
And set to (1, 0) as the both defaults are, doesn’t work. (0, 0) seems to be the only working combi. I think this issue was also present in horologist (https://github.com/google/horologist/issues/245).
Any thoughts on this are appreciated.
Update: It is worth to mention that my items are two full screen elements. After I scrolled the screen, the code behaved like I had set (0, 0).
item {
Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
Text(text = "Hello World!")
}
}
ScalingLazyListState
and autoCentering
of ScalingLazyColumn
are not the same, the code doesn’t work.
val listState: ScalingLazyListState = rememberScalingLazyListState(
initialCenterItemIndex = 0,
initialCenterItemScrollOffset = 30
)
...
ScalingLazyColumn(
autoCentering = AutoCenteringParams(itemIndex = 0, itemOffset = 0)
The construct of state and autoCentering is somehow confusing.John Nichol
08/05/2022, 12:09 PM@Composable
fun SLCLargeItemsNotVisible() {
val state = rememberScalingLazyListState()
ScalingLazyColumn(
modifier = Modifier.fillMaxSize(),
verticalArrangement = Arrangement.Center,
state = state,
autoCentering = AutoCenteringParams()
) {
items(4) {
Card(
onClick = {},
modifier = Modifier.height(300.dp),
) {
Box(modifier = Modifier
.fillMaxSize()
.background(Color.Blue))
}
}
}
}
Yingding Wang
08/05/2022, 2:40 PM@Composable
fun fullScreenImage() {
Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
Image(
painter= painterResource(R.drawable.watch_preview_circular_384),
contentDescription = "Yellow fullscreen"
)
}
}
@Composable
fun fullScreenText() {
Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {
Text(text = "Hello World!")
}
}
will open an issue report.https://github.com/yingding/autoCentering/blob/main/video/NotShowingImageAtStart.mov▾
https://github.com/yingding/autoCentering/blob/main/video/showImageAtStart.mov▾
John Nichol
08/06/2022, 9:32 AMImages
I don't have any immediate ideas why it would matter what the type of content is - but with a repro case I am sure we will soon get to the bottom of it.Yingding Wang
08/09/2022, 11:43 AMJohn Nichol
08/09/2022, 12:06 PM