Create a 'container view' and add the view with bindings as a
subview to it. The container view's drawRect can just be a NOP.
Then, call enterFullScreenMode:withOptions: on the container view.
I have not played with those new full-screen APIs, so not sure if
this would work or not. However, since the view with bindings would
then have a non-nil superview, bindings would not go away when going
full-screen.
I haven't tried this either, but I can't think of a reason off-hand
why it wouldn't work.
I often find myself using just plain NSView objects as containers for
organizational purposes. This has only increased with the
introduction of NSViewController in Leopard. It's my new favorite
class! Mmm, modularity.
These days I typically create an NSViewController subclass for
whatever higher-level "component" I'm designing, and have its view be
a plain NSView that acts as a container for everything else within the
module (buttons, text fields, table views, etc.).
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
