Re: [ve-dev] Commit intercept for dropped components?

[Gerald Rosenberg <gerald@xxxxxxxxxx>]

At 12:55 PM 6/22/2006, you wrote:

> As I recall, your
> internal model is basically the info describing the current state of the
> FormLayoutEditPolicy. My suggestion is that when a change occurs, you
> simply mark your current model as stale. And then the next time you need
> the data you can reconstruct it. 

Sorry I was not clear.  My internal model is keeping significantly
more information that can be reconstructed from the remote VM -- the
model is tracking defined, but currently unused constraints as
well.  

If I use VisualComponentAdapter#componentValidated() I would need to
reconcile, rather than reconstruct.   I think I can do that,
but ...

1) Is there any better alternative approach?

2) On completion of a drag-move of a component between containers, is VE
supposed to generate "EditPartListener#removingChild" and
"EditPartListener#childAdded" events against the respective
containers? 

Thanks,
Gerald