Skip to main content
gamedev.net
🔒 Locked

WTF

Started by ItalicBold Sep 18, 2000 at 4:26 AM 1 replies 750+ views
Original Post
ItalicBold
ItalicBold
Small Prob perhaps some of you could help me with this. This loop causes for some unknown reason a major slowdown on my computer, unless I have the debug.print after the primary.blt? Why could this be? the prob is definitely with the primary.blt '' Main Loop Do Blit DoEvents Loop Sub Blit() On Local Error GoTo ErrorOut '' Blit Fisrt Buffer To Primary DirectX.GetWindowRect FormMapEditor.PictureMap.hWnd, BlitBlock Primary.Blt BlitBlock, Buffer, BlitBlock, DDBLT_WAIT Debug.Print ErrorOut: End Sub
It is better to have an idle mouth as oppose to an idle conversation.Consequences only serve to enhance the experience of expressing ones freedom to choose.
Facehat
Facehat
I''m guessing that it''s because calling debug.print yields to the system for a moment. I cant think of any other reason for why it''d do that.

----------------------------------------
"Before criticizing someone, walk a mile in their shoes.
Then, when you do criticize them, you will be a mile away and have their shoes." -- Deep Thoughts
ItalicBold
ItalicBold
Thanks, I thought it was as much. I am now only blitting when i need to from events, it works better this way.
It is better to have an idle mouth as oppose to an idle conversation.Consequences only serve to enhance the experience of expressing ones freedom to choose.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.