OpenEuphoria

Re: Win32Lib bug

• Posted by Derek Parnell <ddparnell at bigpond.com> Mar 31, 2001
• 633 views

I'll check it out tonight. Can't think of anything of hand that wold have
targeted pixmap behaviour. I remember testing the Black Box games etc and
they all worked fine though. In the new v0.56 I had to move some
initialization out of the onOpen handler to the new onActivate handler but
that was all.

------
Derek Parnell
Melbourne, Australia
"To finish a job quickly, go slower."

----- Original Message -----
From: "David Cuny" <dcuny at LANSET.COM>
To: "EUforum" <EUforum at topica.com>
Sent: Saturday, March 31, 2001 5:32 PM
Subject: Win32Lib bug


>
>
> I ran into a problem porting my Minesweeper clone to the latest version of
> Win32Lib. It's also tripped me up with other games I've written. The
problem
> is that Win32Lib doesn't allow the creation of zero-sized pixmaps.
>
> In a number of my programs, I would 'create' a zero-sized pixmap as a
> placeholder, and later replace it with a 'real' pixmap once I had
calculated
> the pixmap.
>
> In the old version of Win32Lib, you could create a zero-sized pixmap, and
> the library would just set the handle to null. Resizing a 'real' pixmap
> would discard the old version and replace it with a new version. Resizing
a
> 'null' pixmap should simply create a new pixmap, and ignore the old value.
>
> The behaviour in the current release is a bit different. I can create the
> zero-sized pixmap, but I can't resize it. So when I try drawing to it
later
> (after it's been resized) I get lots of errors, and no image.
>
> Other than identifying the general problem, I haven't bothered to find out
> what has changed, or why. The temporary fix is to create a non-zero sized
> pixmap. But I'm still curious how the behavior changed, and why.
>
> Thanks!
>
> -- David Cuny
>
>
>
>