Important: API Change Questions

These are important so please answer explaining your understanding of
the following issues.

 o  PosChange removal
    * replaced by trapping x/y puts?
    * if so, no way to track movement of boxes in a grid
    * unless grid boxes have x/y put to but not written?

 o  SizeChange removal
    * replaced by trapping width/height?
    * does core put to width/height when placing/sizing boxes?
    * if it does, it won't write to min/max values - inconsistent

 o  ChildChange/numchildren
    * everybody prefers ChildAdded/ChildRemoved
    * ChildChange mandates always checking against indexof(child)
    * which are you going to go with?

I do not really understand your intentions for trapping x/y and
width/height to simulate PosChange and SizeChange.  It's just seems like
they are inadequate solutions or that they introduce blurry contexts.

It's a bit difficult to adapt to API changes if you refuse to explain
them, so I'd really appreciate a reply on this matter.
-- 
- Charlie

Charles Goodwin <[email protected]>
Online @ www.charlietech.com