🚀 go-pugleaf

Hi folks.  I've found a few annoying things in IB, which I thought I'd share,  
in the hopes that someone here might have some insight.  First the bugs:

When you load a palette into IB, IB initializes each of the objects in the  
palette. Fine.  When you quit IB, or even when you unload the palette, IB does  
not send a quit or a free message to any of these objects.  What's the problem,  
you say?  In the palette-unloading case, what's a few bytes between friends,  
and in the IB quitting case, all the memory for tha process will get freed up  
anyway, so who cares?  Well, in my case, each of the objects on the palette is  
acutally a proxy for another (set of) process(es) somewhere out on the net  
which get started up when that object gets initialized.  When IB quits, and  
doesn't warn my proxy object, the processes which it's connected to don't  
realize it's gone until much later (if at all).  I can work around this, but  
it's still incorrect behavior. Bug.

As has been discussed to death, once you load a palette into IB, as long as the  
path to it is valid, it will continue to show up in your preferences.  You  
should be able to select and delete one of these from inside IB, and you can't.   
Bug.

Now to the suggestions:

IB is very good about if you subclass something and don't provide an inspector,  
IB will let you use its superclass's inspector.  Unfortunately, as soon as you  
provide an inspector, you no longer get access to the superclass inspector.   
For example, let's say you have a class Foo which has a lot of info on it's  
inspector panel, one set of which is a 4x4 matrix.  You now subclass Foo to  
FooBar.  It would be nice if you could put only FooBar specific info on its  
inspector and not have to replicate (among other things) the 4x4 of its  
inspector.

Finally, can someone explain the philosophical difference between an  
IBInspector and an IBEditor?  I know how to implement both, but I'm not sure  
which is appropriate for what...

Hopefully, someone has some suggestions...

later.

--

-->  Michael B. Johnson
-->  MIT Media Lab      --  Computer Graphics & Animation Group
-->  (617) 253-0663     --  wave@media-lab.media.mit.edu
-->  NeXT Mail accepted at  wave@nordine.media.mit.edu