Hello, I want to move the whole UI logic + rendering, which is based on flash, on a separate thread, while the game logic will be on the main thread.
Have any of you met this problem and how did you solve it?
Do think it is practical to make any part of the UI multithreaded, or it should be left in the main thread, since there might be a lot of synchronization in some screens between the UI thread and main thread?
Well, I'm not a flash developer but mostly it's not a great idea to put the UI stuff on a different thread than the main thread. As you already said it might get you in trouble because of the synchronization between the main and the UI thread.
I remember when I was doing some JavaFX stuff, that every UI call needed to be on the main thread otherwise the UI elemets doesn't get called/updated at all. Better put everything else to seperated threads.
How complex is your UI? How responsive do you want it to be? Why do you want to implement it on a separate thread?
Well the reason I want to implement it on separate thread is the performance. The UI is complex - it has windows, sliders, pop-ups, etc.
You just have to render it to a separate plane and if you're not running that low-level then render-to-textures and implement your own double or triple buffering.
It's worth looking for an extension to get a plane if you try it.
I'm not sure where the notion of fast-enough UI code is coming from - in my experience it's the slowest thing there is.
In cars we use separate threads for overlays because they are so slow and we have to meet performance targets for rendering gauges.
I'm not sure where the notion of fast-enough UI code is coming from - in my experience it's the slowest thing there is.
