Re: make that dataSource (was Re: an interesting delegate design issue raised by IB...)
Re: make that dataSource (was Re: an interesting delegate design issue raised by IB...)
- Subject: Re: make that dataSource (was Re: an interesting delegate design issue raised by IB...)
- From: "Michael B. Johnson" <email@hidden>
- Date: Wed, 12 Sep 2001 20:48:28 -0700
Excellent suggestion! I actually already do this for hotkeys (I have a
similar scheme for delegating (in this case I am using the term correctly
:-)) the responsibility of what to do when I get a keyDown: to a
"WKHotKeyHandler" delegate that handles it, so that while I, as a class
designer, might come up with some set of hotkeys that I like to zoom
in/out, go fullscreen, go to the next image, etc. the application you're
using the object in might have different hot keys, so I decided to make
this configurable from inside of IB. This allows for customizing hot keys
in the same way (i.e. all instances in a nib could use a shared delegate
in the nib or one provided by the File's Owner, or keep their own), and
needs it own inspector panel (because you need all the space to show all
the selectors and actions, and let the user map key presses on them).
It's an excellent suggestion to have the contents of the image view (if it
has its own images) as its own panel.
On Wednesday, September 12, 2001, at 04:15 PM, Enrique Zamudio wrote:
I was working on something totally unrelated to this, and suddenly I had
an
idea that might work for you:
Write a custom inspector that will show you the images that your image
view
has. That way you can have a simple handling mechanism (through your
internal
data source), that will let the user delete an image that was previously
added, or replace one, change the order (in case that matters), etc.
Some objects use that kind of interface; for example when you're working
with
EOF in IB, you can select a textfield and see its Association Inspector,
which only appears in textfields that have associations to display groups.
Your image view could have some other inspector besides the regular ones
(size, connections and attributes) to manage all the images in its
internal
data source.
Just an idea...
eZL
--> Michael B. Johnson, Ph.D. -- email@hidden
--> Studio Tools, Pixar Animation Studios
-->
http://xenia.media.mit.edu/~wave