Well, a thread wrapper in orx wouldn't help you much as long as orx isn't multi-threaded/thread safe itself.
That being said, I've been thinking on different multi-threading approaches for orx itself, but time has been lacking and it's not very high on my priority list right now.
When the time comes though, I'll go for an approach that will use as less mutex/locks as possible and favor some clock-based data-driven sequencing scheme. Something akin to Shears would be great.
But we're not there by any stretch.
When the time comes though, I'll go for an approach that will use as less mutex/locks as possible and favor some clock-based data-driven sequencing scheme. Something akin to Shears would be great.
But we're not there by any stretch.
Awesome PPT! I should be studying game development, I love this!
Comments
Well, a thread wrapper in orx wouldn't help you much as long as orx isn't multi-threaded/thread safe itself.
That being said, I've been thinking on different multi-threading approaches for orx itself, but time has been lacking and it's not very high on my priority list right now.
When the time comes though, I'll go for an approach that will use as less mutex/locks as possible and favor some clock-based data-driven sequencing scheme. Something akin to Shears would be great.
But we're not there by any stretch.
Awesome PPT! I should be studying game development, I love this!
Beside, Shears' main author is a very good friend of mine so I can't say bad things publicly!
jajaja shurely :P