Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-ui-dev] Progress Monitor threading leads to undesired code execution order

What is the correct way to handle this situation?

1. CellEditor in a TableViewer is active.
2. User takes action which results in an event which causes the focusLost() to be triggered on the active CellEditor.
3. The CellEditor#modify method spawns a progress monitor in a separate thread.
4. The action triggering the focusLost() event is then processed while the progress monitor is working.
5. The rest of the CellEditor#modify method is executed.

I'd like step 5 to occur prior to step 4.  So far the fix has been to filter out other events until the progress monitor completes. 

Back to the top