Re: controls not rendered, sometimes
Re: controls not rendered, sometimes
- Subject: Re: controls not rendered, sometimes
- From: Christian Pekeler <email@hidden>
- Date: Fri, 26 Mar 2004 22:46:17 -0700
Argh! Not solved. The problem just doesn't happen as often anymore.
Christian
On Mar 26, 2004, at 18:53, Christian Pekeler wrote:
Solved: I realized that some of my controls had their nextKeyView
outlet set. Disconnecting them made my problem go away.
Also, if I leave the custom nextKeyView chain in place, and not invoke
a method which is disabling some of the controls in
awakeFromInsertion, the problem goes away, too.
So it seems that a custom nextKeyView chain involving controls which
are disabled in awakeFromInsertion causes some controls to not render
themselves.
If I find some extra time, I'll try to create an isolated testcase and
submit it as a bug.
Sometimes when my app starts up, some NSControls are not being
rendered
in the main window until I resize it. They actually show up for a
split
second at the beginning and then disappear immediately. I only seem to
be having this problem when the window starts off with its minimal
size. Those problematic NSControls are subviews of a splitview, next
to
other controls in the same splitview which always get rendered
correctly. Except for their locations, the controls which get rendered
don't seem to be different from those that don't. If I configure the
window to be textured, the problem goes away, i.e. all controls are
always rendered when the app starts up. Sending the (non-textured)
window a -display in -awakeFromNib doesn't help as a workaround.
Has anyone seen such a problem and know of a solution?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.