Hi Jesse - this might be obvious, but have you tried using the
"setOpaque" method? It could trigger some redrawing or whatever as
necessary to reflect the change.
Yeah, I tried that and many other combinations of ordering windows
out and in...
Which brings up a question: why override isOpaque when you could
just use setOpaque?
Now that's a good question.
At some point a long time ago I got it stuck in my head that there
was no setOpaque: method (there isn't in the NSView class), but yes I
see it now in the NSWindow class.
That was easy, thanks!
Jesse
I have an NSWindow subclass that has overridden isOpaque.
Depending on the users settings that method can return either YES
or NO as the application runs. The problem is that NSWindow only
seems to recognize the first value returned, and after that the
window state doesn't seem to change no matter what I'm returning
from the isOpaque method.
Does anyone know what needs to be done to an NSWindow to get it to
recalculate it's isOpaque status?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
