Hi Beatrix,

yes of course. In other ADKs we have it.

Maybe Xojo itself will do what you need.

Let's wait then they ship it

Hello Beatrix,

As I understand it, you must avoid running time-consuming tasks in the main thread. That thread is mainly for UI, so it would not be "non-responding" states in this scenario.

So, I believe Xojo provides some way to call functions in another thread - right? Or do you think we need to periodically call "yield" from every V4RB method (like we did for diagnose, reindex)?

I believe in being prepared and in testing.

For the main tasks my app already is threaded with a clear separation between database tasks and UI. But it's still easy to get the beachball. Just this morning a user told me that he deleted some data, saw the beachball and then force-quit the app because he saw "not-responding". I've been telling you that this is a problem for at least 10 years if not longer.