Finally I have completed my Final Year Project using Jetpack Compose UI only.🥳 Thank you so much for helping me throughout the projects.

does the

7094152

snapshot of accompanist have been released properly or still there are some files to be uploaded? I’m getting read timeout for metadata.xml

How can I achieve snapping like behavior in LazyRow? is there any built-in method to do that?

Does anyone have any recommendations around presenting a Snackbar once? Driving the UI from state is easy except when I want to present something at a particular point in time, and only once. I could create state that contains something like

showSnackbar

, but if my UI gets recomposed because of a configuration change the Snackbar will show again. Is the recommended approach to handle the timing in whatever produces state, and after a period of time output state with

showSnackbar = false

?

Can we add a "content description" to an image in compose?

Hey everyone, What is the correct way of dealing with state and ComposeNavigation? I’m facing an issue where the same code works fine for simple composable but doesn’t work when wrapped inside of a NavHost. Code snippets and details in the thread…

I’m using compose snapshot

7094152

and found that

LaunchedEffect

no longer accepts subject which used to re-launch the

block()

on value changes. What is the alternative then?

When I try to make TextField pre-focused using

onActive { focusRequester.requestFocus() }

keyboard doesn’t open, when focused manually, it works fine, what could be the issue? is there any other way of doing the same? also, I noticed

onActive { }

callback is getting deprecated. What should we use instead?

I’m getting

ClassCastException

for String to AnnotatedString when passing in String to

TextFieldValue

in Compose snapshot

7094152

Stacktrace ⤵️

@Composable
Outer() {
  profileResult = viewmodel.field.observeAsState()
  Inner(profileResult)
}
@Composable
Inner(myProfileResult: ProfileResult){
    NavHost(
       navController = editProfileNavController,
       startDestination = EditProfileScreen.EditProfile
    ) {
       Timber.d("profileResult1 ${myProfileResult.workEducationItems}")
       composable(EditProfileScreen.EditProfile) {
            Timber.d("profileResult2 ${myProfileResult.workEducationItems}")
            ScrollableColumn(
                 modifier.padding(top= 100.dp).fillMaxSize(),
                 horizontalAlignment = Alignment.CenterHorizontally
            ) { ....
}

Hi guys, I have a question related to recomposition of NavHost Composable. When the data is refreshed, 

profileResult1

  holds the new data but 

profileResult2

  still hold the old data (even it is recomposed). Anybody has any idea why this is happening 😄 Any solution for that other than passing with Ambient 😄 Thanks!

Hi. I try to put some CustomView that extended EditText. It’s work fine except backspace doesn’t delete current text. Anyone found this problem before? This is simple Example Code

@Composable
fun TestScreen() {
    val context = AmbientContext.current

    val nativeView = remember {
        EditText(context)
            .apply {
                layoutParams = ViewGroup.LayoutParams(MATCH_PARENT, WRAP_CONTENT)
           
                addTextChangedListener {

                }
            }
    }

    Column(modifier = Modifier.fillMaxWidth()) {
        Text(text = "Some Label")
        AndroidView(viewBlock = { nativeView })
        Text(text = "Some Text")
    }
}

I can reproduce in this case Pixel2XL Android11 -> Keyboard ManMan But in below list.  It’s work fine Pixel2XL Android11  -> GKeyboard Oneplus7t Pro Android10  -> Keyboard ManMan Oneplus7t Pro Android10  -> GKeyboard

launchInComposition is gone? Why?

I'm always a little surprised when I see people using

AndroidView

directly in their apps, and maybe it's because we made the API too pleasant to use or maybe it's because we never really communicated the intent to the community. 🤷. Certainly I never expected to see people remembering the view and then just referencing that view in the

viewBlock

, I suppose no API survives first encounter with the user. Composables are epitomized by their convenient declarative APIs. The older android Views often have imperative APIs with sometimes surprising semantics that need to be papered over, and this wallpaper isn't always straight forward to get right. The intent/expectation was that users would write a composable function who's sole purpose was to wrap a particular Android View, and would provide this wallpaper, such that the widget was pleasant to use in the rest of their application. Maybe we need to make AndroidView have some more boilerplate and look uglier 😛 😉🤣

Testing question (learning about testing composables) This may be a silly question but I have a really simple composable. It's just two

Text

s. (you could even argue that this shouldn't be a separate compasable) Either way it's legitimately being used in my app and now I've been watching @ppvi (it says Jose if offline, so hopefully that doesn't ping him. Wasn't my intention.) compose testing talk and I want to write a test, but I've never really tested individual views before (not an android and not in any language) and now I'm not sure what to really assert. Maybe since it's such a contrived example there's not much to test and so it's actually a bad candidate, but should I just test that my composable is there with the text that I passed in the parameter? Any guidance would be appreciated.

Does using ViewPager as an AndroidView in Compose only app is a good approach for now? Or it can be easily done in Compose?

I find myself doing a lot of nested Columns inside of Rows and vice versa kinda like LinearLayout horizontal and vertical in Android view land. Having a deep enough heirarchy was viewed as a possible perf issue and so something like constraint layout was helpful. In compose, do I have to worry about having really nested Cols and Rows?

I feel like I know the answer to this question... but I'm going to ask it anyway. Iterating on a Composable and viewing the Preview in a new project is much faster (still not blazing fast) but definitely faster than a large existing project that I already have where we just added compose. Is it possible to just have an @Preview not have to rebuild the full project if the full project is needed? I realize it's probably easier said than done, but something like this

@Preview(showBackground = true)
@Composable
fun Beep(){
    Text("Boop")
}

is just interesting that it takes like 5 minutes in my old project (because my existing project is super large it just builds slow overall) vs in a brand new project. What am I actually after? I want to be able to create and iterate on composables quickly and I feel like it might just be easier to create composable in compose-desktop and then just copy pasta back into my actual app.

does anyone have a problem importing the dependency

androidx.ui:ui-tooling:1.0.0-alpha10

?

Execution failed for task ':samples:android:mergeDebugResources'.
> Could not resolve all files for configuration ':samples:android:debugRuntimeClasspath'.
   > Could not find androidx.ui:ui-tooling:1.0.0-alpha10.
     Searched in the following locations:
       - <https://kotlin.bintray.com/kotlinx/androidx/ui/ui-tooling/1.0.0-alpha10/ui-tooling-1.0.0-alpha10.pom>
       - <https://dl.google.com/dl/android/maven2/androidx/ui/ui-tooling/1.0.0-alpha10/ui-tooling-1.0.0-alpha10.pom>
       - <https://jcenter.bintray.com/androidx/ui/ui-tooling/1.0.0-alpha10/ui-tooling-1.0.0-alpha10.pom>
     Required by:
         project :android

Hi, this question is more about guidance because I'm not sure where to start. I have a

TextField

, and to highlight of the text with colours, say given a list of words to highlight. Basically - syntax highlighting. The image attached gives you an idea of what I mean. Would I have to make my own

TextField

component for this?

How can I navigate from the VM in jetpack compose? say I’ve fetched some data and I need to navigate after the data has been retrieved

Hello everyone ! Is there a reason why we cannot create our own custom brushes by extending Brush()?

Hey all. Can someone chime in for a problem I am having? I wanted to create a slider style button where additional actions are hidden beneath. The current setup is as below. And I can't get the surface below the card to register taps. Does moving the top layer card not expose tap-able surface of the view beneath?

Box {
        Card(...) {
            Row(...)
            ) {
                Surface(
                    modifier = Modifier
                        .fillMaxHeight()
                        .fillMaxWidth(0.5f)
                        .clickable(onClick = { ... }),
                    color = Color.Red
                ) {
                    ...
                }
                Surface(modifier = Modifier.fillMaxSize().clickable(onClick = { ... }), color = Color.Blue) {
                    ...
                }
            }
        }

        Card(
            modifier = Modifier
                .fillMaxWidth()
                .height(boxHeight)
                .padding(horizontal = 40.dp, vertical = 16.dp)
                .swipeable(
                    state = swipeableState,
                    anchors = anchors,
                    thresholds = { _, _ -> FractionalThreshold(0.3f) },
                    orientation = Orientation.Horizontal
                )
                .offset { IntOffset(swipeableState.offset.value.roundToInt(), 0) }

        ) {
            Row(verticalAlignment = Alignment.CenterVertically, modifier = Modifier.clickable(onClick = { ... })) {
                ...
            }
        }
}

Passing

Resources

into a composable as a parameter? 👍 or 👎

Any ETA when Compose will come to beta? Also, would a beta release be ready for production?

Is it possible to scope a viewmodel to a navigation graph with navigation-compose?

Has anybody tried using the modifier verticalScroll and/or scrollable to preserve the scroll position in a LazyColumn list when doing something like viewing a image in fullscreen and then coming back to list . Also how do I see the code in below package androidx.compose.foundation.samples.VerticalScrollExample

Might

slideInVertically

slideOutVertically

be buggy? The initialOffsetY/ targetOffsetY should return the half of the content's height but this doesn't match. My content's height is 120 dp but value returns 376 dp 🤔

@Composable
fun SlideVerticallyAnimationComponent(
    visibility: Boolean,
    offset: Int,
    content: @Composable () -> Unit
) {
    AnimatedVisibility(
        visible = visibility,
        enter = slideInVertically(initialOffsetY = { value ->
            Timber.e("valueIn: $value") // output: 376 dp
            offset
        }) + fadeIn(),
        exit = slideOutVertically(targetOffsetY = { value ->
            Timber.e("valueOut: $value") // output: 376 dp
            offset
        }),
        content = content
    )
}

is https://gist.github.com/gildor/82ec960cc0c5873453f024870495eab3#file-jetpackcomposescaffoldsnackbar-kt-L102 the best way to close the keyboard using a button? I cant find how to create or reference my own SoftwareKeyboardController. Is there no composable function for this

I am trying to use a

Text

or

TextField

to display a repeating decimal, e.g., 2.(0123456789) (I am resorting to parentheses notation because to the best of knowledge, Android does not support overline, as discussed on this channel last week: https://kotlinlang.slack.com/archives/CJLTWPH7S/ ). The problem I have now is that line breaking rules will break the line after the "." (FYI it breaks up ".(" but not ".1(", for example).  I’ve been trying to look for a solution but I really only found this 9-year old one for the regular UI (and it seems like overkill in any case): https://stackoverflow.com/questions/6134457/how-to-prevent-edittext-from-breaking-a-line-after-punctuation.  What I want is a line break only when the text string (in my case digits with other characters like "(", ")", "/", "+", "-", etc.) exceeds the width of the view. Essentially I just want the line breaking rules turned off. Can this be done in Compose? (I am porting a prototype of my app that uses JavaFX, which breaks lines as I desire.)