Fa3ien <fab### [at] yourshoesskynetbe> wrote:
> That's what I meant : implement the "transformation history" using SDL.

> If the SDL is powerful enough, it could even be automatic : each time
> something tranforms an object, an "event" mechanism adds the transform
> to the history.

  Why do objects need a transformation history? Why would you waste memory
in such a thing?

  The current SDL does not need a "transformation history" nor does the
new one. That's because the SDL code itself is the "transformation history".
Why do you need to store it in two places?

> Objects could even have some kind of "extended data" that could be attached
> to them, and be used as the user wishes. (it would help things like
> parent-chlid relations between objects)

  Why waste memory in something which will seldom be used?

  Wouldn't it be better to make a SDL where you can create a new version
of the object with the "extended data" instead? That way if you have
100000 objects in your scene and only one of them needs the "extended data",
memory is not wasted for useless "extended data" in those 99999 other
objects.

-- 
                                                          - Warp

Post a reply to this message