[ULC-developer] Problem with selection events in two synchronized table trees

[ulc rbeeger]

Hi!   We have a component that is similar to the fixed column table tree on the code community - two table trees side by side with sychronized expansion and selection. We originally synchronized the selections in the two table trees like this: right.getBasicTableTree().getBasicTable().setSelectionModel(left.getBasicTableTree().getBasicTable().getSelectionModel());   Visually it all works wonderful. The selection spans both table trees and a change in the selection is processed in both table trees seamlessly. The only problem: selections in the right table tree don't trigger any selection events on the server side ULCTableTree - neither on the right nor the left one.   The code from the code community adds two listeners to the two table trees and synchronizes the selection after it happens. While we now get the events for selections in both table trees on the server, this solution has an ugly effect: The synchronization of the selection is clearly visible. You see that for example the selection changes from the first to the third row in the left table tree and then you see how it changes in the right table tree. This effect tears the two table trees visually apart. Does anyone have any idea how to ensure events are fired for selections in both table trees without the ugly effect.   Thanks in advance,   Robert