Bug 283470 - Non-forked modal-context blocks UI
Summary: Non-forked modal-context blocks UI
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: Workbench (show other bugs)
Version: 1.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 17:58 EDT by Benjamin Muskalla CLA
Modified: 2010-07-16 09:36 EDT (History)
2 users (show)

See Also:

Attachments
demo patch (2.43 KB, patch)
2009-07-14 17:58 EDT, Benjamin Muskalla CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Muskalla CLA 2009-07-14 17:58:17 EDT 
Using a IRunnableWithProgress (eg. in a Wizard) without forking it blocks the whole UI of RAP as we don't have a UICallback there.
This is pretty silly when you do a long running task in a dialog as the user has no clou that something is really happening.

The main problem is ModalContext#run which runs the IRunnableWithProgress in the UIThread.
One idea could be to hijack the IProgressMonitor we pass into the ModalContext so somehow update the clientstate at least with every "worked" call (just an idea, no clou if this could possibly work)
Comment 1 Benjamin Muskalla CLA 2009-07-14 17:58:59 EDT 
Created attachment 141577 [details]
demo patch

Patch for demo to show the problem