[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] RCP e4 and EASE
|
Hi all,
I am getting forward with my RCP 4 application. My main issue is now due to this problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=283490
The RCP application (UI thread) thread calls "fEngine.executeSync(content)", because I want to read the script results and show them on the GUI. When I call now " showQuestionDialog("", "")" then I get a deadlock. The UI thread is blocked due to "fEngine.executeSync" and "UIModule" is also blocked because of " Display.getDefault().syncExec()".
The deadlock does not occur if I use " fEngine.executeAsync". Waiting with "fEngine.isIdle()" is not working, because it doesn't wait until " Display.getDefault().syncExec()" returns.
Is there a good way around this issue?
Beside that it only UIModule and ScriptService need to be modified a bit to make it workable for a e4 application. "isHeadless" needs to be changed to check if ScriptService has a workspace set. ScriptService needs to be enhanced by a getter and setter method for the current workspace. I set the workspace from the e4 application during startup.
Calls like this: " PlatformUI.getWorkbench().getWorkbenchWindows()[0].getSelectionService()" need to be changed.
I am working now on a UIModule_e4 module that I will hopefully be able to upload, when I have solved my current issues.
-----Ursprüngliche Nachricht-----
Von: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] Im Auftrag von Christian.Pontesegger@xxxxxxxxxxxx
Gesendet: Donnerstag, 12. Oktober 2017 14:19
An: ease-dev@xxxxxxxxxxx
Betreff: Re: [ease-dev] RCP e4 and EASE
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ease-dev
