October 11, 2018 at 10:20 am #600350
Sorry that you are seeing this problem. Thank you for the screenshots and the log file.
It looks like a problem with Oomph. Oomph attempts to track and reapply preferences saved into a directory under User Home. This can cause fighting with styling preferences that our theme sets.
Can you please shut down Eclipse, go to your user home/.eclipse folder, remove folders that have oomph in their name, start Eclipse, then set the syntax highlighting color and see if it is retained.
The errors in the log are most likely caused due to our plugins not having full write access to your workspace. If possible, please switch to a new workspace and check if the reported issues persist.
Apologies for inconvenience caused. Please let us know how the above suggestion works for you.
Genuitec SupportOctober 11, 2018 at 11:04 am #600355
I have switched to a new workspace, on a different physical disk. This does seem to solve the problem and the syntax is retained after restarts! Thank you.
Is there any way that I can give the plugins full write access to my workspace? I would love to keep my workspace in my C:/Users/Luuk/Documents/Development folder, in stead of moving it to a different disk.
Before switching to a new workspace, I have tried the steps of your first suggestion. This did not work for me. I have removed the directories indicated in the picture. The directories reappear after restarting Eclipse btw.
Thanks again for your help.
Attachments:You must be logged in to view attached files.October 11, 2018 at 11:12 am #600357
I managed to give the plugins full write access to my workspace by right clicking the workspace directory, and deselecting ‘Read-only’. I then applied this to all subfolders and files within this directory. Now I have fully retained syntax using my original workspace.
Thank you so much for your support!
EDIT: I spoke too soon. Using only the original workspace does not allow me to retain the syntax coloring. Any suggestions how I can give Eclipse plugins full access to my original workspace?
October 12, 2018 at 3:19 am #600413
- This reply was modified 1 year, 10 months ago by luuk80.
To guarantee that Eclipse has full access to the workspace, you could specify a non-existent directory when starting Eclipse and Eclipse would create the workspace folder and everything in it which would mean it has full access. If Eclipse doesn’t start up, then there is likely a problem with the folder access.
So what you can do is point Eclipse to a non existent folder under
C:/Users/Luuk/Documents/(let Eclipse create it and do not create the folder yourself outside of Eclipse) when starting Eclipse and then see if the syntax coloring changes are retained in the said workspace.
Please let us know how it works for you.
Genuitec SupportDecember 29, 2018 at 12:11 pm #605949
I’m having the same problem. However disabling the DevStyle Startup Experience seems to fix the problem for me.December 31, 2018 at 7:17 am #606040
Thank you for posting the workaround details.
Can you please clarify if you are seeing the same problem in a new workspace (pointing to a non existent folder) as well when the DevStyle Startup experience enabled?
Apologies for inconvenience caused.