Maybe, a specific async-task or concurrent-task only may be the best option for multi-threading on EKG.
If running ekg::update() on a different thread, the flow is totally loss (draw glitch, crazy behaviors etc); the way I am thinking to do is using a specialized threading task executor with future. May work better.
Note: The tasks executed must be the application-side only, and not pre-allocated internal tasks (such as reload, sync, gc, etc); due the address pointless issues.
The current status of threading on EKG is 0%, but soon I must fix this issue. Thanks, meow.
Maybe, a specific async-task or concurrent-task only may be the best option for multi-threading on EKG.
If running
ekg::update()on a different thread, the flow is totally loss (draw glitch, crazy behaviors etc); the way I am thinking to do is using a specialized threading task executor with future. May work better. Note: The tasks executed must be the application-side only, and not pre-allocated internal tasks (such as reload, sync, gc, etc); due the address pointless issues.The current status of threading on EKG is 0%, but soon I must fix this issue. Thanks, meow.