[bugs #12158] Custom views in gorm and NSCoding problem

[Gregory John Casamento]

Follow-up Comment #2, bugs #12158 (project gnustep):

Another way to approach this is to use the "CustomView" which doesn't invoke
initWithCoder: when it's unarchived.   The only method which is called in
this case is initWithFrame: (per docs).   

The best way to do this, if you need to be able to inspect the extra
attributes on an instance of the new class is to create a palette, as
described before.  Palettes allow you to write inspectors and editors which
can allow the user to manage the extra attributes.

If you have a Mac, you will find that the same behavior is apparent there as
well, if you use non-keyed coding. :)

Gorm, and IB, use proxy objects to facilitate the use of custom classes which
they don't know about.   Some of this is covered in the Gorm documentation.

    _______________________________________________________

This item URL is:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=12158>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/