The difference is that plain modifiers like width() take into account layout Constraints while required modifiers like requiredWidth() ignore them. You can think of constrains as min/max width/height of a measured element. To better understand how layout modifiers and constraints work take a look at this post. Let’s see an example of width modifier, height … Read more
We have a separate package for that, which is pretty useful. There are two main extension functions that would be suitable for you: pointerInput – docs pointerInteropFilter – docs If you want to handle and process the event I recommend using pointerInteropFilter which is the analogue of View.onTouchEvent. It’s used along with modifier: Column(modifier = … Read more
To have smart recomposition scopes play a pivotal role. You can check Vinay Gaba’s What is “donut-hole skipping” in Jetpack Compose? article. Leland Richardson explains in this tweet as The part that is “donut hole skipping” is the fact that a new lambda being passed into a composable (ie Button) can recompose without recompiling the … Read more
It’s a feature of Compose about scoping and smart recomposition. You can check my detailed answer here. What really makes your whole Composable to recompose is Column having inline keyword. @Composable inline fun Column( modifier: Modifier = Modifier, verticalArrangement: Arrangement.Vertical = Arrangement.Top, horizontalAlignment: Alignment.Horizontal = Alignment.Start, content: @Composable ColumnScope.() -> Unit ) { val measurePolicy … Read more
It’s supposed to re-measure a component based on another component size… SubcomposeLayout doesn’t remeasure. It allows deferring the composition and measure of content until its constraints from its parent are known and some its content can be measured, the results from which and can be passed as a parameter to the deferred content. The above … Read more
I found a solution created by Samir Basnet (from Kotlin Slack Channel) which was useful for me, I hope it helps someone else… @Composable fun CollapsingEffectScreen() { val items = (1..100).map { “Item $it” } val lazyListState = rememberLazyListState() var scrolledY = 0f var previousOffset = 0 LazyColumn( Modifier.fillMaxSize(), lazyListState, ) { item { Image( … Read more
For a complete answer you can use ClickableText which returns the position of text, and UriHandler to open URI in a browser. val annotatedLinkString: AnnotatedString = buildAnnotatedString { val str = “Click this link to go to web site” val startIndex = str.indexOf(“link”) val endIndex = startIndex + 4 append(str) addStyle( style = SpanStyle( color … Read more
Warning: Ian Lake is an Android Developer Advocate and he says in this answer that pass complex data structures is an anti-pattern (referring the documentation). He works on this library, so he has authority on this. Use the approach below by your own. Edit: Updated to Compose Navigation 2.4.0-beta07 Seems like previous solution is not … Read more
When button finds tap event, it marks it as consumed, which prevents other views from receiving it. This is done with consumeDownChange(), you can see detectTapAndPress method where this is done with Button here To override the default behaviour, you had to reimplement some of gesture tracking. List of changes comparing to system detectTapAndPress: I … Read more
I prefer using SharedFlow for a job like this: class OneShotOperationViewModel : ViewModel() { private val _toastMessage = MutableSharedFlow<String>() val toastMessage = _toastMessage.asSharedFlow() fun sendMessage(message: String) { viewModelScope.launch { _toastMessage.emit(message) } } } @Composable fun TestScreen() { val context = LocalContext.current val viewModel = viewModel<OneShotOperationViewModel>() LaunchedEffect(Unit) { viewModel .toastMessage .collect { message -> Toast.makeText( context, … Read more