@kittaakos , we do have one issue that I don't expect has an easy fix. In the DialogAnswerProvider, you once changed, as I recall, Display.getDefault().syncExec(() -> {
to
Display.getDefault().asyncExec(() -> {
warning of a potential deadlock.
I think we've learned that if you move around the console window, as in move it to a different screen or change focus--not sure exactly what--it results in a deadlock between the getting a lock in the dialog window and getting a lock (?) for the console window, to which logging is going.
As I said, I don't expect an easy fix but thought I'd ask...
@kittaakos , we do have one issue that I don't expect has an easy fix. In the DialogAnswerProvider, you once changed, as I recall,
Display.getDefault().syncExec(() -> {
toDisplay.getDefault().asyncExec(() -> {
warning of a potential deadlock. I think we've learned that if you move around the console window, as in move it to a different screen or change focus--not sure exactly what--it results in a deadlock between the getting a lock in the dialog window and getting a lock (?) for the console window, to which logging is going.
As I said, I don't expect an easy fix but thought I'd ask...