NSTrackingArea strange requirement
NSTrackingArea strange requirement
- Subject: NSTrackingArea strange requirement
- From: rajesh <email@hidden>
- Date: Wed, 26 Nov 2008 15:30:58 +0100
Hi all,
I have Custom NSView with set of boxes arranged in some pattern
( boxes with some extra UI elements like , text fields and stuff).
I am using the gaps between the boxes a.k.a the visible custom NSView
to add the NStrackingAreas for cursor updates and as well for resizing
the subviews (i.e the NSBox)
As an obvious fact , when ever I try to resize the subviews I need to
as well set the frame for the NSTrackingArea elements and here I is no
such thing as setFrame
I googled around and found that , everybody is alloc-init ' ng and
then set the tracking area to 'nil' or release and create a new
NSTrackingArea then – initWithRect:options:owner:userInfo: and use it.
I don't have fixed number of subviews or as a fact no fixed gaps ,
hence the tracking areas count might shoot up to anything.....
I think following the general approach will have a serious affect on
efficiency , memory and other factors .....
I can't use SplitView to manage the resizing of subviews ( I iterate,
no fixed subview , and I need to collapse or expand a particular
subview )
am I missing any obvious approach or is that I got off on wrong foot
Any help is appreciated
regards
Rajesh_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden