Am 13.07.10 15:34, schrieb Eric Moffatt: > > Lars, I agree wholeheartedly. > > One of the reasons for having a live editor is to help ensure that > *legal* changes to the model get reflected in the UI. This is really > just a matter of timing I think. By the time this missing functionality > was reported we were all completely swamped with the SDK work... > > Here's a quick comment about each defect (I'll update the defects after): > > _https://bugs.eclipse.org/bugs/show_bug.cgi?id=318383_ I think that > this would work if the 'move' were broken down into a 'remove' followed > by an 'add(index)'...we can look into an optimized 'move' later
I've fixed that now in the live editor codebase which uses add/remove when working with a live model. I still think we could easily add the Notification.MOVE which means an item changed index in the list (=> move can only happen inside a list => no container change!) I've also fixed https://bugs.eclipse.org/bugs/show_bug.cgi?id=318246 in the live-editing mode because the renderer somehow expects that I call ElementContainer#setSelectedElement() after the move. Tom -- B e s t S o l u t i o n . a t EDV Systemhaus GmbH ------------------------------------------------------------------------ tom schindl geschaeftsfuehrer/CEO ------------------------------------------------------------------------ eduard-bodem-gasse 5/1 A-6020 innsbruck phone ++43 512 935834 _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
