Re: stk::rectangle

I am beginning to feel the same way.  I had to wrap most of the rect
functions to add the on_resize signal anyway.  Perhaps we should revert
to the "has a" model and remove all the virtual crap from rectangle.=20
Let's discuss this thoroughly before we make any changes to the source
though, this needs to be the last time we change how rects and widgets
relate.

Darren

On Sun, 2003-10-19 at 05:29, Marc Str=C3=A4mke wrote:
> Hi team,
> I have just looked at the changes darren commited today, and have found=20
> out that rectangle contains virtual functions, do you guys really think=20
> thats good? Imo we should create rectangle_interface class or something=20
> to derive from, and not use the regular rectangle. These changes make=20
> rectangle easyli a few 100 bytes(!!!) Big, this is really not the right=20
> thing to do for an object which the user expects to be lightweight is=20
> it? Imo we only got two options, either we stop deriving from rectangle,=20
> or we create two rectangle classes, one which serves as an interface and=20
> from which you can derive, so it behaves like a rectangle but isnt one,=20
> but we really shouldnt continue with using a struct full of virtual=20
> functions everywhere in the code, this is a major source of bloat!
>=20
>=20
>=20
> _______________________________________________
> Libstk mailing list
> [email protected]
> http://www.dvhart.com/cgi-bin/mailman/listinfo/libstk