Skip to main content

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

Eli, could you please post this in the eclipse.platform newsgroup, and 
I'll follow up there?

>From the mailing list signup page:
Technical questions and discussions about using eclipse and eclipse-based 
tools, and developing plug-in tools should be posted to the newsgroups. 
Mailing lists at are intended for use by developers actually 
working on or otherwise contributing to day-to-day development. The 
development mailing lists are the way design and implementation issues are 
discussed and decisions voted on by the committers. 


Eli Groesbeck <drelig@xxxxxxxxx> 
Sent by: platform-ui-dev-bounces@xxxxxxxxxxx
12/16/2005 02:17 PM
Please respond to
"Eclipse Platform UI component developers list."


[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 
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. 
platform-ui-dev mailing list

Back to the top