Austin Nelson
02/02/2022, 1:55 AMyschimke
02/04/2022, 3:03 PMfun navigateToPlayer(clearBackstack: Boolean = true) {
val route = NavigationScreens.Player.route + "?page=0"
if (clearBackstack) {
while (navController.popBackStack()) {}
navController.navigate(route)
} else {
navController.navigate(route)
}
}
yschimke
02/07/2022, 10:45 AMJohn Nichol
02/10/2022, 6:13 AMLebron James
02/10/2022, 7:36 AMAndrew Leung
02/10/2022, 1:43 PMLebron James
02/11/2022, 2:44 AMlouiscad
02/21/2022, 9:53 PMLebron James
02/23/2022, 9:39 AMlouiscad
02/26/2022, 10:27 PMremember { … }
, State
, and other Compose facilities for interactive and animated Watch Faces. Is there a reason we don't have such an API? I'd think maybe there would be some performance concerns, or other potential issues, or maybe just bandwidth?
I'm wondering about that because I am pondering about hacking around to use Compose to control what gets rendered on my Watch Face.yschimke
03/03/2022, 9:30 AMJohn Nichol
03/09/2022, 6:21 PMlouiscad
03/12/2022, 8:02 PMyschimke
03/14/2022, 11:25 AMkey(currentBackStackEntry?.destination?.route)
but surprised I needed to. Is this expected? Am I doing something wrong with when I'm accessing a state field? Or is it a bug in PositionIndicator?yschimke
03/16/2022, 9:30 AM건유1019
03/20/2022, 12:32 PMAustin Nelson
03/20/2022, 7:02 PMyschimke
03/20/2022, 8:27 PMprivate fun screenshot(screenshotName: String, block: @Composable () -> Unit) {
composeTestRule.setContent {
RememberTheMilkTheme {
Scaffold(timeText = {
TimeText(timeSource = FixedTimeSource)
}) {
block()
}
}
}
composeTestRule.onRoot().assertIsDisplayed()
val context = InstrumentationRegistry.getInstrumentation().context
val isScreenRound = context.resources.configuration.isScreenRound
Screengrab.screenshot(screenshotName, WearScreenshotStrategy(isRoundDevice = isScreenRound))
}
yschimke
03/23/2022, 8:57 AM@Test
fun testAutoHide() {
composeTestRule.setContent {
VolumePositionIndicator(
modifier = Modifier.testTag(TEST_TAG),
volumeState = { volumeState },
autoHide = true
)
}
val positionIndicator = composeTestRule.onNodeWithTag(TEST_TAG)
positionIndicator.assertDoesNotExist()
volumeState = volumeState.copy(current = 51)
composeTestRule.mainClock.advanceTimeByFrame()
composeTestRule.mainClock.advanceTimeBy(500L)
composeTestRule.onRoot(useUnmergedTree = true).printToLog("testAutoHide")
positionIndicator.assertIsDisplayed()
}
John Nichol
03/24/2022, 9:54 AMCurvedRow
CurvedLayout
API including a DSL for describing curved components. Also some APIs moved from experimental to public (such as SwipeToDismissBox) with some minor API updates. PositionIndicator
has had some updates to allow control over positioning, better handing of unscrollable contents, etc. Finally some UX updates to ScalingLazyColumn
scaling parameters and CircularProgressIndicator
size, padding and track colors.Yingding Wang
03/25/2022, 8:05 PMRendering sandbox error
to use the compose preview with ui-tooling:1.2.0-alpha06
in Bumblebee. Really like Devices.WEAR_OS_SQUARE
and Devices.WEAR_OS_SMALL_ROUND
from compose 1.2.0 in Preview
By turning off the rendering sandbox seems to solve the issue, is it recommended to do so? My apology if it is an off-topic question.
@Preview(
apiLevel = WEAR_PREVIEW_API_LEVEL,
uiMode = Configuration.UI_MODE_TYPE_WATCH,
backgroundColor = WEAR_PREVIEW_BACKGROUND_COLOR_BLACK,
showBackground = WEAR_PREVIEW_SHOW_BACKGROUND,
showSystemUi = false, // the android system bar on top
device = Devices.WEAR_OS_SQUARE
)
@Preview(
apiLevel = WEAR_PREVIEW_API_LEVEL,
uiMode = Configuration.UI_MODE_TYPE_WATCH,
device = Devices.WEAR_OS_SMALL_ROUND
)
@Composable
fun WearAppPreview() {
WearApp()
}
Bernt Julian
04/07/2022, 10:06 AMLebron James
04/08/2022, 10:24 AMandrew
04/15/2022, 12:43 AMandrew
04/19/2022, 3:13 AMJohn Nichol
04/20/2022, 6:13 PMYingding Wang
04/25/2022, 1:10 PMToggleChip(
modifier = modifier,
checked = checked,
toggleControl = {
ToggleChipDefaults.switchIcon(checked = checked)
},
onCheckedChange = {
checked = it
},
Is there any additional steps in toggleControl
I will need to display the switch icon as that of Alpha 20?yschimke
04/30/2022, 8:24 AMbarat
05/02/2022, 9:11 AMjava.lang.IllegalArgumentException: Inconsistency between the count of nodes tracked by the state (0) and the children count on the SubcomposeLayout (2). Are you trying to use the state of the disposed SubcomposeLayout?
I thinks it is a same issue on compose issueTracker accompanistIssue
I need version 1.0.0-alpha21 to use edgeSwipToDismiss in my pagerScreen.
According to the issue tracker above, it seems that the version of compose need downgrade.
Does anyone know the solution?Lisandro Di Meo
05/05/2022, 1:39 PMSwipeDismissableNavHost
I've found that the swiping gesture is ignoring the BackHandler
inside the composable. For example, if my nav graph is: A -> B -> C, and the swipe from C should redirect to A.
I think I have to custom some behavior of the SwipeToDismissBox, but I'm not sure how. Any help is appreciated!
composable(
Paths.WORD,
arguments = listOf(navArgument("language") { defaultValue = "EN" })
){ navBackStackEntry ->
BackHandler() { navController.navigate(Paths.HOME) }
CompleteWord(navController, listState, completeWordViewModel, navBackStackEntry.arguments?.getString("language")!!.toLanguage())
}
Slack Conversation