11 Feb
2010
11 Feb
'10
10:24 a.m.
Philip Pemberton wrote:
Creating, say, a window is a piece of cake -- extend
the wxFrame
class, add your components to the constructor (stuff like "myTextBox =
new wxTextBox(this)"), and add event handler functions to deal with
what the user does.
<Way OT rant>
The thing that's currently pissing me off about wx is that the newer
ones lack the rawbits interface - at least on OS X 10.6 - and some on
Linux as well.
Well, that and the fact that you can't blit an image to a DC, you have
to first convert it to a bitmap.
wxBitmap can be manipulated with rawbitmap.h - only it's not available
where I need it.
wxImage can be manipulated with the SETRGB macro , but you need to
convert it to a bitmap before you can Blit it, and doing so is insanely,
unbearably slow on OS X.
Oh sure, there are other methods of playing with wxImages, but they're
even slower (using pens, drawing lines, etc.)
Worse yet, on OS X 10.6 with wxCocoa, if I use wxImage with SETRGB and
then convert the image to a bitmap and blit the bitmap, I'm get weird
banding artifacts when using the gray 50% desktop pattern (you know,
alternating lines of 0x55 and 0xaa patterns black & white), but not on
the older OS X 10.5's. It's making it very hard to get a 64 bit version
of LisaEm.
That and playing sounds is fugly - you have to pass it a .wav file, so I
had to resort to creating a temporary .wav file on the fly and telling
it to play that. Oh sure, on SOME platforms passing raw data works, but
not everywhere.
Rest of the stuff is wonderful.
:-)
</WAY OT>