OpenEuphoria

RE: win32lib v0.57.7

• Posted by Brian Broker <bkb at cnw.com> Jun 04, 2002
• 529 views

Hi Don,

What version of Win are you running?  Grabbing the DC does nothing to 
correct the problem on my Windows 98 [Version 4.10.1998] system.  But if 
it's really true, it might be one heck of a clue in the right direction.

-- Brian

PS to Derek:  I'd love to see the program that smokes.bmp belongs to 
(tobacco's a vegetable ya know 

Don Phillips wrote:
> >Good question. I've only tested it on WinMe.
> >
> >Okay, I just tested it on WinNT and it works fine.
> >
> >It does seem to be a Win9X issue. Great! Now how do I get aound that! 
> >Any
> >ideas anyone?
> 
> Very strange results.  I dont really know what to say.
> 
> If I run it as is, after about 1/2 seconds it starts to paint on the 
> desktop 
> or another window and it freezes shortly after.  Now dont ask me why, 
> but if 
> I grab the window DC at the start of the timer routine it acts just fine
> 
> 
> procedure Tick( integer timerID )
> 	sequence s
> 	atom hDC1
> 
> 	hDC1 = w32Func( xGetDC, {getHandle(Win)} )
> 
> 	drawBackground()
> 	moveSprites()
> 	moveShip()
> 
> 	-- draw the screen
> 	copyBlt( Win, 0, 0, Buffer )
> end procedure
> onTimer[ Win ] = routine_id( "Tick" )
> 
> 
> Heck... im not even *using* the DC I got back (or releasing it).  Just 
> added 
> the variable and grabbed the DC and everything clears right up.  Dont 
> really 
> know how this applies to the Win32Lib routines though.  Since I am not 
> releasing it I would think it would just create even more leaks... 
> *shrug*
> 
> 
>