Re: [patches] rendering optimizations, backed out one optimization

WTF?

> Context:
>
> [removed PosChange, childadded, childremoved, added ChildChange

After you _explicitly_ acknowledged that we _need_ PosChange for doing
_anything_ useful with interacting with non-packed boxes, you then go and
remove PosChange anyway.

Are you being absent minded or bloodey minded, Adam?  Whichever, it's
equally annoying.  Please fix this ASAP.  I absolutely, 100% _refuse_ to
use the simplex core if this is not rectified or there is a satisfactory
recourse.

- a very annoyed Charlie