Flutterby™! : Mac development woes

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Mac development woes

2006-04-19 21:32:28.822617+00 by Dan Lyke 3 comments

Aaaaugh! You know it's bad when a widget set makes you pine for Windows, in this case it's the wackiness of Apple's "Carbon". Trying to redraw a window? You have two different ways to invalidate the region, depending on whether the window is semi-transparent or not, either via InvalWindowRect(...) or HIViewSetNeedsDisplay(...). Of course neither of these is doing anything for the particular control (that's very explicit about tellling me that it doesn't own any of the data it's a view on), because there I have to call UpdateDataBrowserItems(...).

[ related topics: Apple Computer Microsoft Software Engineering Macintosh ]

comments in ascending chronological order (reverse):

#Comment Re: made: 2006-04-20 18:44:49.575245+00 by: markd

Carbon's underpinnings predates windows by a bit. That's why many (many) mac developers use the NeXTStep Cocoa toolkit.

#Comment Re: made: 2006-04-21 02:46:18.795598+00 by: Dan Lyke

Yeah, it's something of a political discussion on this project. If I had my way, we'd be using something modern and flexible like GTK, but that has its own set of limitations.

And... uhhh... Don't Cocoa's underpinnings predate Windows by a bit? Heck, I think even Tk's do, and that intelligently handles resizing...

#Comment Re: made: 2006-04-21 16:15:59.559918+00 by: markd

Windows 1 was ca 1985, The first NeXTCube came out in 1987 timeframe. The difference in elegance between the two APIs is stunning.

Depending on your platform needs, GNUstep may be an option (if you're targeting the linux folk). Not really an option if you're aiming for the windowsfolk.