On Apr 5, 2009, at 11:30 AM, Michael Ash wrote:
On Sat, Apr 4, 2009 at 10:20 PM, Jo Meder <[email protected]> wrote:
Hi,
I'm in the planning stages of porting the Mac back end of my cross
platform
UI framework from Carbon to Cocoa, because I need 64 bit GUI
support. It
looks like it should be relatively straightforward. I'm already
using some
Obj-C++ and Cocoa APIs for stuff like cursor management and drawing
text
into graphics canvases.
The one thing I'm not really clear on is what the Cocoa equivalent
of a
Carbon user pane control would be. It seems that there isn't really
a direct
equivalent in Cocoa and that the best way to do things would be to
have a
custom view inheriting from NSControl. Would that be right?
Can you explain what a user pane is (not all of us are that familiar
with Carbon) and what exactly you're trying to do?
A user pane was a precursor to HIView, that is a view (control is the
proper term for the user pane) that could handle user input events,
drawing and adding sub-views for grouping purposes. NSView is the
equivalent of HIView so NSView is what you want I think.
From a cursory search on the term, it seems that a custom NSView
subclass is what you want. Whether you'd want to inherit from
NSControl or not depends on whether NSControl provides any
functionality you desire.
Mike
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/thealchemistguild%40gmail.com
This email sent to [email protected]
Regards,
Josef
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
