Re: frozen window
Re: frozen window
- Subject: Re: frozen window
- From: "Erik M. Buck" <email@hidden>
- Date: Wed, 30 Jan 2002 13:15:21 -0600
>
That was it, all right. Now I'd like to hear an explanation of this. Why
is
>
that two out of three options for the window's backing store give me a
>
frozen window? If only one option gives me a functioning window, why are
>
the other two there at all? Thx - m.
>
--
>
You have found one of the new bugs that Apple has introduced when throwing
babies out with bath water. Different backing stores used to work with
Display Postscript. Quartz broke all backing store options except
"buffered". Therefore don't use anything except buffered in a Cocoa
application.
The loss of backing store options is a tiny inconvenience and a small loss
of an optimization option. There are much bigger problems like the fact that
the Foundation framework classes have been de-optimized and the semantics
of -setNeedsDisplay: are completely broken. Both of these things make all
Cocoa applications slower than they used to be on much less powerful
hardware.
In many way Apple is a shining light of software design and development. In
many ways Apple seems to be glaringly incompetent. I guess that I have just
described most successful companies. I am looking back with rose colored
glasses to the NeXT days which were not perfect, but in many ways were
better than now.
My off the top of my head complaints with what Apple has done with
Openstep->Cocoa:
1) Apple dropped promised and functional inexpensive cross platform support
2) Apple has seriously degraded graphical performance in spite of much more
powerful hardware. I concede that Apple has added new graphics capabilities
also.
3) Apple has done absolutely inexcusable things like breaking the semantics
(and supposed optimization) of -setNeedsDisplay: making all Cocoa
applications slower. I have volunteered to fix this for them for free.
4) Apple has in many ways degraded the Openstep->Cocoa documentation
5) Apple has not and does not provide adequate Cocoa training
6) Apple has mixed Carbon and Cocoa in ways that I do not find aesthetically
pleasing.
7) Apple has dropped Objective-C EOF for no good reason
8) Project Builder has been degraded for Objective-C development (but added
Carbon/C++ and Java support)
9) Help Viewer
10) What were they thinking with Sherlock ? Does anybody like it ? Where
is DigitalLibrarian ?