This is reply on posting with quite undescriptive title 'Few questions'
>
> > 3) Can one object own another objects ?
>
> Well... I'm not sure. That probably depends a bit on what you want to do
> with them. The "Group" object owns a list of object, but that object needs
My idea is simple one object owns another object. Owned objects can't be
placed outside parent object. Parent object should (for example) resize to
fit children size changes. Both parent and child will have graphical
representation.
May be the Group object do exactly what I wrote above. I wasn't
investigate the sources inot deep details.
> What exactly is it you want to do?
I'm interested in object properties because I was doing something similar
before. More precisely I started to ...
I now have some basic concepts and some pieces of code which are far from
publishing.
Main concepts are:
* property sets are independent on objects (thus object of any type may
have property 'Color', so color may be edited for any selected group if
object)
* Properties are edited in PropertyEditor which is specialized window
based on GtkCTree widget and is common for all objects (if you have
seen Delphi Object Inspector you know what I am talking about). Main
benefit of this aproach is that object producer have not to create
property dialog box for each object he is creating and all property
handling is present in DIA core.
>
Steve
