[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] -setTarget: and -setAction: enabled in NSImageView
From: |
Kazunobu Kuriyama |
Subject: |
Re: [PATCH] -setTarget: and -setAction: enabled in NSImageView |
Date: |
Wed, 24 Dec 2003 11:55:09 +0900 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 |
Hi Fred,
Fred Kiefer wrote:
Alexander Malmberg wrote:
Kazunobu Kuriyama wrote:
I want to second Alexanders position here. The documentation from
Apple is rather thin on what change should happen. On the other hand
it is rather clear on what should not be changed. NSImageCell should
remain a subclass of NSCell and not of NSActionCell.
So I asked more than one time why NSImageCell needs to be a subclass of
NSCell. Do you know any document that makes this point clear? If there's
one, it would give a good foundation for our discussion, reducing
perception gap. Anyway, the new behavior of Cocoa's NSImageView seems
not to be documented yet. Should we be prudent till an updated
decumentation is available?
We need to investigate further and the best way to do this, would be
to write a program on a MacOSX machine and watch it closely. Without
this test I would suggest, that we only make changes to NSImageView
adding target and action ivars (with setters and getters and encoding)
and adding a sendAction call to the performDragOperation: method.
This looks to me another possible solution. Because I don't know the
details of ObjC runtime, I can't evaluate possible impact on applications
when extra ivars is added to a library. Can I do this safely?
Re: [PATCH] -setTarget: and -setAction: enabled in NSImageView, Kazunobu Kuriyama, 2003/12/23