Dear community, I would really use some help with the following problem.
The environment is latest neon target platform, running on Ubuntu 16.04, Fedora 24 and down.
I am starting my e4 RCP application with the following option:
The first launch fails and it took me a while to figure out the reason - missing xmi file:
How do I make the workbench load without this file for the first time??
There are absolutely no traces on where and why it fails to load.
The workbench.xmi is produced when application gets closed for the first time.
And I don't get a chance of the first time.
When I manually produce this file by running the application without --launcher.GTK_version 2 switch - it works.
Using default GTK3 is out of the question, it just doesn't work at all and we simply have no means to figure out the compatibility issues.
If someone would tell me how to power up into GTK2 we would be able to wait until GTK3 SWT issues get resolved.
I remember I had to export SWT_GTK3=0 when testing Neon on Ubuntu 16.04
I doubt your problem has anything to do with the missing workbench.xmi. It is recreated if it does not exist on the next start (or on initial start).
Thank you for the reply.
Yes, it is true, this was an internal issue in the application itself, not related to workbench.xmi after all.
I have gotten into an array of problems within neon-linux-gtk3-swt and the way to force the application fall back into gtk2 was quite painful.
So, this question was a side effect resulting from the struggle and can be safely ignored.