Re: surface ++= ?

On Apr 15, 2004, at 5:20 PM, Charles Goodwin wrote:

[talking about detecting when the surface property changes]

> Or, even better, we could just compare the 'surface' property from
> within the core when a box changes parent, since that will support
> self-emulation and dynamically generated surface objects.

That is what I was saying. The problem is Box.java doesn't know what 
the surface property is. All it can do is call the appropriate traps to 
find it. If those traps return a different object each time you can't 
tell when the surface has actually changed.

> I also don't think we should be passing 'true' but rather the new
> surface object, simply because it gives a nice way of accessing the old
> surface object through 'cascade'.

That doesn't work. The value of the surface property comes from the 
trap placed within surface.t. When you become a child of a new surface 
you can't cascade back to the old one. We could put the *old* surface 
value to surface then you could use cascade to get the *new* surface. 
That seems kind of backwards though.

This shouldn't be this hard....

-Brian