G
Guest
But in a weird way...
BackgroundWorker creates another background worker that updates the UI
through a series of ReportProgress calls - works fine.
Thread A
----> creates and spins up Thread B
Waits for a signal from Thread B to proceed
Upon signal, a MessageBox is displayed to gather Yes/No.
DialogResult return sets semaphore for Thread B to terminate and calls
Join.
IF I do not specify an IWin32Window in the MessageBox call, all is well...
except that the MessageBox can occasionally get lost behind the application.
If I specify any window, including the main UI thread, I get:
"This operation has already had OperationCompleted called on it and further
calls are illegal." This all comes from a ReportProgress call. From what I
can gather, the thread still wants to loop as before.
Any thoughts?
BackgroundWorker creates another background worker that updates the UI
through a series of ReportProgress calls - works fine.
Thread A
----> creates and spins up Thread B
Waits for a signal from Thread B to proceed
Upon signal, a MessageBox is displayed to gather Yes/No.
DialogResult return sets semaphore for Thread B to terminate and calls
Join.
IF I do not specify an IWin32Window in the MessageBox call, all is well...
except that the MessageBox can occasionally get lost behind the application.
If I specify any window, including the main UI thread, I get:
"This operation has already had OperationCompleted called on it and further
calls are illegal." This all comes from a ReportProgress call. From what I
can gather, the thread still wants to loop as before.
Any thoughts?