Re: Important: API Change Questions

On Mon, 2004-04-19 at 01:00 -0700, Adam Megacz wrote:
> Charles Goodwin <[email protected]> writes:
> >  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?
> 
> Right now the best idea on the table is to let you "pin" one box to
> another so that x.distanceTo(y) is held constant.  However, I'm not
> 100% sure how to do that, or how to deal with nonsensical stuff like
> circular constraints, etc.

Perhaps you could allow the trapping of b1.distanceto(b2).x and
b1.distanceto(b2).y - that wouldn't require much work.  Just a
test(DIST_IS_TRAPPED) and a for loop shooting through relevant boxes.

> I really don't think this is a crisis.  I'm not dead-set against going
> back to ChildAdded/ChildRemoved.  But there are much more important
> things to deal with right this moment than a simple naming convention.

I never said this was a crisis.  You simply ignored us on the issue.

Thing is, unlike you, I use Ibex.  (Yes, being facecious there but
correct at the same time.)  I have to chop and change code every time
you change the API on a whim.  If you'd simply ask us about something
you admit is 'a simple naming convention' then perhaps we'd immediately
agree on the final version rather than swimming through a few versions
and forcing, erm, me to switch between each one to keep up.
-- 
- Charlie

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