On approximately 5/14/2004 7:22 AM, came the following characters from
the keyboard of Jez White:
Hi,
Would any one have any objections if I change (fix depending on your
viewpoint:) ) the BeginPaint and EndPaint functions in GUI.xs?
I think these functions are left over from previous versions (along with
the other painting/drawing functions in GUI.xs). They are currently not
used by any other internal functions, nor are they documented anywhere.
The general usage would stay the same, but I plan to return the details
as an array (dc,x,y,x1,x2,flag) rather than messing with the object
itself. I think this would be cleaner, faster and more like other xs
functions.
In general usage these functions would be used in conjunction with a
Hooked WS_PAINT message, allowing the users program to handle the
painting of window directly. A good example, would be the bitmap
scrolling example ask for by Glenn Linderman, instead of painting the
bitmap into a image control, it could be painted direct into the windows
DC (I'll try and put together an example this weekend).
Comments?
I'm in favor for a several reasons, one of them selfish :)
1) I've never used them, so it won't affect me (and that's not the
selfish reason)
2) From a brief look at the functions, it sounds like an improvement in
clarity, and possibly speed.
3) There's a good chance the functions will get better documented as a
result, so people that didn't take the time to figure them out before,
may get a benefit from them with this change... (hint, hint) :)
4) If I get a nice scrolling bitmap example code, I'll be really happy,
and withdraw my request for adding back the old Win32::GUI::MDI object.
(Yep, this is the selfish one, but slightly altruistic as well.)
--
Glenn -- http://nevcal.com/
===========================
The best part about procrastination is that you are never bored,
because you have all kinds of things that you should be doing.
