@Sedit,
Some attempts were made in the past to update DarkGDK, I think in some ways you suggested. However many of those changes failed to compile, and others severely crippled performance. The result was a completely broken, uncompilable version that was ultimately useless and then left for dead. So in the interest of having a latest compilable version, when I found it that way, I sent a request to Lee Bamber for check-in privileges to the official repository and then I regressed to earlier versions of offending modules as a quick fix, as well as fixing a few things and making a handful of improvements... ultimately resulting in r113 (official). r114 is, of course, the latest and I assume the best starting point by now. I think @s_i can tell you about that and where to get it. However, you may be interested to glance at some of the offending versions I removed... that is if you can find a way to still access them. Google has since halted and archived the repository, and I'm not sure if earlier versions and their check-in comments are still accessible.
The archived repository is here:
http://code.google.com/p/darkbasicpro/
Although since those earlier versions didn't work, it'd probably be simpler to just forget them anyway and make your own updates, starting with the r114, and with your vision for updates. I'm hardly personally familiar with r114, but as of r113, there were a plethora of inefficiencies still remaining in the code. I think @WickedX addressed some of those in his r114. But with all the updates in video hardware and DirectX since DarkGDK was created, If I were just coming on the scene today, I'd probably not bother with DarkGDK, but just create my own wrapper from scratch at this point.
One piece of advice when dealing with commercial software though (such as Microsoft)... the historical track record has been that often the latest, fanciest, or most popularly-used or recommended software features are severely inefficiently implemented (such as a 20:1 slow-down) under the hood, and one would be ill-advised to use them blindly without evaluating their performance first. Also, just because some college professor teaches or mega-corporation "recommends" (sells) them doesn't mean they're advisable to use. Never assume anything from "authorities" or "official" or corporate dogmas. Hear and consider those others, learn what you can from them. But be a scientist... Test it. Always measure and observe for yourself, and trust your own observations.
Good luck!
Judging what we see is the greatest blinder and self-limiter in the universe.
What we perceive is never reality. It is only a story we tell ourselves based on our current perspective, which has far more to do with our beliefs about ourselves than with anything else.
