I’m trying to display a dialog as soon as the current view renders. However, the dialog is shown twice (maybe due to how recomposition works) and requires two dismisses to disappear.

I’m trying to display a dialog as soon as the current view renders. However, the dialog is shown twice (maybe due to how recomposition works) and requires two dismisses to disappear.

I’m trying to display a dialog as soon as the current view renders. However, the dialog is shown twice (maybe due to how recomposition works) and requires two dismisses to disappear.

I am learning MVI and I have a question about rebuild user interface when state changes. As MVI will have only 1 state, whenever I add new value the state will be changed. So if my state let’s say have 2 list, students and teachers, when I add new value to one list(the other will be the same as I use copy()) will both list be rebuilt ? and if so how can I prevent this.

I wanna use a state holder class to keep some app level state things, for example, if a dialog must be displayed. For that, I added title and message variables in the app state holder class. When I set them to a value different from null, that should display a dialog on my app, because I’m checking if these variables are different from null for displaying it on my screen composable. Something is not working because when I set these variables to a value different from null nothing happens. It seems that recomposition is not being started.

I wanna use a state holder class to keep some app level state things, for example, if a dialog must be displayed. For that, I added title and message variables in the app state holder class. When I set them to a value different from null, that should display a dialog on my app, because I’m checking if these variables are different from null for displaying it on my screen composable. Something is not working because when I set these variables to a value different from null nothing happens. It seems that recomposition is not being started.

I wanna use a state holder class to keep some app level state things, for example, if a dialog must be displayed. For that, I added title and message variables in the app state holder class. When I set them to a value different from null, that should display a dialog on my app, because I’m checking if these variables are different from null for displaying it on my screen composable. Something is not working because when I set these variables to a value different from null nothing happens. It seems that recomposition is not being started.

I am new to both Kotlin and Compose. Using some online guides I have been able to create some very simple UIs. I now have a problem that one of my UIs will not recompose when I use a property of a class within a composable. Below is my code. I create a class that has an INT property which is initialized to 3 and a method that will increase the property’s value. I am using the property value in the text of a button.

I am new to both Kotlin and Compose. Using some online guides I have been able to create some very simple UIs. I now have a problem that one of my UIs will not recompose when I use a property of a class within a composable. Below is my code. I create a class that has an INT property which is initialized to 3 and a method that will increase the property’s value. I am using the property value in the text of a button.

I am new to both Kotlin and Compose. Using some online guides I have been able to create some very simple UIs. I now have a problem that one of my UIs will not recompose when I use a property of a class within a composable. Below is my code. I create a class that has an INT property which is initialized to 3 and a method that will increase the property’s value. I am using the property value in the text of a button.