NSDrawerWindow - using it is okay?
NSDrawerWindow - using it is okay?
- Subject: NSDrawerWindow - using it is okay?
- From: Simon Liu <email@hidden>
- Date: Fri, 18 Mar 2005 12:33:03 +0000
Hi,
If a view e.g. tableview is inside an NSDrawer, invoking -window on
the tableview returns an NSDrawerWindow, which is a private AppKit
class.
When invoking -keyWindow on the NSDrawerWindow, it returns the same
value as what the drawer's parent window should return. This leads me
to believe that NSDrawerWindow contains a reference to the parent
window and passes on (certain) messages to it. Is this limited usage
safe? (Yes, I know, rule of thumb should be to avoid using private
classes which can change...)
I have subclassed tableviews, outlineviews and cells for custom
drawing purposes, and some of the highlighting is based on whether or
not the tableview's window is the keyWindow or not. It's quite
'elegant' and easy to be able to invoke -window, -keyWindow without
worring whether the window is a NSWindow or NSDrawerWindow. Otherwise
I'll have to go and get the NSDrawer and invoke -parentWindow... Not a
big deal, but would be interested in any comments.
---
Regards,
Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden