Hmm... i think the timer idea is quite good,
kinda like you have one loop which is run realtime and then you can set loops up to run at a specific interval.
I mean i use the same sort of thing as i do in DB to make sure I have a timer within C++ for Physics basis, but having that taken out of the equasion certainly would speed up development of things.
But not have it so you have to set it in the main loop because then those calculations you want to run as fas as, can still do so
I think some of you have sidestepped the point here and thats actually giving a pipeline to DBpro coding.
If you think about it we're already working to a pipeline and having to program inline and linear.
Now I don't have a problem with that, however I'd like to be able to create several new windows and have different windows be seperate in use to the original ones.
So like you'd setup the program like
do
pipeloop{
make window 320,240,0,0
print "hi"
pipesync
}
pipeloop{
make window 320,240,400,300
print "click button to exit"
make button("mbok",160,120)
if mouse button("mbok") = 1 then endprogram
pipesync
}
sync
loop
this would allow you to have several programs at once, oki this is more of an application thing - however basically as most people want to also develop thier level editors, music developers and such within darkbasic pro as well - the guys have to relise that these functions are needed just as much as the actual game engine
hope this explains what i ment better.
Anata aru kowagaru no watashi! 
