1) 11 year workaround that steals focus that is no longer relevant. (Removed it).
see:
git show 300ace8e3eaec6136b4861feec65efae8fe149fc
2) MouseDoubleClick event comes after DefaultSelection. Platform UI (quite logically) expects DefaultSelection to come after MouseDoubleClick.
If I manually delay this event by 50ms then all works well.
Now I'm looking for a better way to solve it than a 50ms delay.
What I have in mind at the moment is :
a. Not listen to ROW_ACTIVATION at all. Instead manually trigger defaultSelection after DoubleClick event occurred and get selection manually.
b. Write some thread-wait mechanism that slows down DefaultSelection till after Double-click event went through.
I have a ~Work-in-progress~ patch here: /git.eclipse. org/r/# /c/49702
(NOT FULLY READY YET):
https:/
There are 2 issues:
1) 11 year workaround that steals focus that is no longer relevant. (Removed it). 36b4861feec65ef ae8fe149fc
see:
git show 300ace8e3eaec61
2) MouseDoubleClick event comes after DefaultSelection. Platform UI (quite logically) expects DefaultSelection to come after MouseDoubleClick.
If I manually delay this event by 50ms then all works well.
Now I'm looking for a better way to solve it than a 50ms delay.
What I have in mind at the moment is :
a. Not listen to ROW_ACTIVATION at all. Instead manually trigger defaultSelection after DoubleClick event occurred and get selection manually.
b. Write some thread-wait mechanism that slows down DefaultSelection till after Double-click event went through.
I'm researching which of those works best.
Any thoughts/ tips/advise is welcomed.