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.
Which brings up a question: why override isOpaque when you could just
use setOpaque?
D
On Nov 30, 2006, at 10:11 AM, Jesse Grosjean wrote:
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?
