I implemented a cocoa application that draws to an NSOpenGLView. The
application was working fine in my MacBook running 10.4.6, but when I
updated to 10.4.7 the application stopped drawing lines and polygons
in wireframe.
I created the application in XCode 2.3
The application draws to an NSOpenGLView. I created the view in
Interface builder 2.5.4, by first subclassing an NSOpenGLView named
TrishearView, and then dragging an NSOpenGLView onto my main window
and setting its custom class to be TrishearView. I follow the
procedure outlined in Hillegass, Cocoa programming book, 2nd.
edition, chapter 29.
I set the attributes of the TrishearView to be: Renderer : best,
Color/Alpha buffer: Default, Depth Buffer: minimum, and Stencil
buffer minimum.
The Initialization methods in my TrishearView.h file are:
initWithFrame:pixelFormat:
and
initWithCoder:
I checked the program and I figured out that the initWithCoder:
method was called when starting the program. This method has the
following lines:
The prepare method has stuff inherent to the view such as lightning,
material model, depth buffer, clear color, perspective calculations,
and antialiasing.
As I said, the program was working fine until I installed 10.4.7 in
my MacBook Pro. After that all lines, or polygons in wireframe are
drawn with the same color as the background. I figured out because I
can see some lines when superimposed on a filled polygon.
The weird thing is that I updated to 10.4.7 in my old PowerBook. I
compiled the project in my old PowerBook running 10.4.7 and the
application worked fine. All lines, polygons filled or in wireframe
display great.
So the problem is in my MacBook Pro running 10.4.7.
I have read in several forums that is not a good idea to set the
pixel format of the NSOpenGLView in Interface Builder. But, this
worked fine in 10.4.6 for both my MacBook Pro and my PowerBook, and
in 10.4.7 for my PowerBook. And it this is so buggy, why is there as
an option (a very convenient option for a beginner like me) in
Interface Builder?
I think that there might be a bug in my program, but at the same time
it does not make sense that the program was working fine under 10.4.6
for both ppc and Intel, and then suddenly when I update to 10.4.7
(courtesy of Apple) it starts doing weird things in Intel. This
certainly defies the definition of an Universal application.
Nestor Cardozo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
