[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -setTarget: and -setAction: of NSImageView

From: Kazunobu Kuriyama
Subject: Re: -setTarget: and -setAction: of NSImageView
Date: Wed, 24 Dec 2003 11:55:59 +0900
User-agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1

Alexander Malmberg wrote:

Kazunobu Kuriyama wrote:


(1) Almost all concrete classes inherited from NSControl are
implemented using NSCell.

No, using a subclass of NSCell. NSImageView uses NSImageCell by default,
but you can also use any other cell class you like, or a custom cell

You are right.  Sorrry for that sloppy explanation.

But they didn't just change the behavior of -setTarget:/-setAction: to
not raise exceptions. Instead (which is what I've been trying to get at
from the start), the relevant behavior change in this case is
"NSImageCell has no target/action" to "NSImageView/NSImageCell sends its
action when an image is dropped on it, if it is editable".

I agree.

Having NSImageCell be a subclass of NSActionCell makes sense now that
NSImageCell has a target and an action. However, it would be contrary to
all (non-GNUstep) documentation, so I'm skeptical.

I also share the same feeling with you to some extent.  So I sent emails
here to hear the views of others.  But should we wait for Apple's updated
document?  This is a point GNUstep makes a decision.  IMHO, I'd like to
go ahead.

Either way, the
effects on custom cell classes and encoding/decoding of the involved
classes needs to be looked at carefully first.

I've failed to pay attension to this point.  Good suggestion to me.
Thank you.

Yes, we now know the full behavior change, so we can now Think Hard
about what to do about it. Thanks! :)

Great.  I'm happy to work with you.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]