progressbar | really basic thread-safe progress bar | Command Line Interface library

Use the Bindings API.

Note that the progress is supposed to be between 0 and 1, so if you are entering percentages, instead of proportions, into your text field you need to divide by 100:

Android is an event driven OS that runs on a single main thread. Drawing is an event. That means in order to draw the main thread needs to return to the event loop. Your code does not return to the event loop until after you do all your processing. Thus it won't draw until after the processing is done.

The way to solve this is to use either a Thread or a Kotlin coroutine to do the processing, and allow the main thread to return to the event loop. BTW, if you have long lasting processing you should not be doing it on the main thread anyway- it freezes your UI and makes your app appear non responsive, for the same reason. The main thread should do short quick calculations and respond to OS events only.

You'll need a common base for the elements you store references too. This could be one way:

This answer explains how, in Elmish.WPF, progress updates to the user interface can be done from an async.

I have created an example on GitHub that demoes this. The example also demoes another way to call async functions and receive results. And it also demoes how to use mkProgram instead of mkSimple. The demo can be used as a starting template for your Elmish.WPF applications.

This snippet from the demo show the essential code involved in updating a user interface from an async.

Both techniques are based on code from the Elmish Book. You will find a lot of code there that is useful also in Elmish.WPF.

I haven't tried to update a progress bar here, only a status text box, but from this you'll very easily figure out what to do to update anything.

You can use painter.state to achieve this

Try this method:

useMemo and useState with useEffect do different things, so you can not convert useState/useEffect 100 % equally to useMemo.

A more or less equivalent useMemo approach would be this (but it doesn't work, other refactoring would then also be necessary, see below):

I think the problem is that you have mixed Material UI version 4 and 5 libraries and they are incompatible with each other. Try replacing @material-ui/core with @mui/core and just remove @material-ui/icons import as you already have @mui/icons-material and use the latest versions of all @mui/* imports.

Clear node_modules before installing dependencies again, to make sure everything is in order and old dependency versions are removed.

EDIT: what turned out to be necessary to solve it in the end - install node v12.22.7, remove node_modules, clean yarn cache and reinstall dependencies