Community
Participate
Working Groups
When you add a new expression in the debug view, the expression remains invisible until editing is finished which evidently makes it very difficult to use. This behavior started recently after an upgrade of Eclipse photon (I have the photon/staging update site in my installation), but I can't exclude that host OS has done some updates at the same time. The latter is a Kubuntu 16.04 with gtk version i3.18.9. The problem vanishes, if Eclipse is started after "export SWT_GTK3=0".
(In reply to Ansgar Radermacher from comment #0) > When you add a new expression in the debug view, the expression remains > invisible until editing is finished which evidently makes it very difficult > to use. This behavior started recently after an upgrade of Eclipse photon (I > have the photon/staging update site in my installation), but I can't exclude > that host OS has done some updates at the same time. The latter is a Kubuntu > 16.04 with gtk version i3.18.9. The problem vanishes, if Eclipse is started > after "export SWT_GTK3=0". Can you post a screenshot? (In SWT land, invisible could mean different things).
Created attachment 273399 [details] After clicking on "Add new expression" After clicking on "Add new expression", nothing happens, beside that the cursor changes to an "enter text" cursor (but it does not move as you type), while I can apparently enter an expression without seeing it. It appears when I press enter.
This looks like a known bug in Table/Tree editing for GTK3.10 - 3.18. In GTK3.20 GTK's drawing model changed (again) which fixes it. GTK3.22 is the stable and final version for GTK3, just as GTK2.24 was for GTK2. Earlier versions of GTK3 (i.e., versions < 3.22) are not as stable and therefore we do not actively develop for them. Ubuntu is one of the last few that still support an OS with GTK3.18, but even this will change when Ubuntu 18.04 LTS is released in a month (it will have GTK3.22). Please try using a newer GTK version, preferably GTK3.22.
I upgraded GTK to 3.22 and it indeed fixed the issue. Thanks for the hint. Close with won't fix? (In reply to Eric Williams from comment #3) > This looks like a known bug in Table/Tree editing for GTK3.10 - 3.18. In > GTK3.20 GTK's drawing model changed (again) which fixes it. > > GTK3.22 is the stable and final version for GTK3, just as GTK2.24 was for > GTK2. Earlier versions of GTK3 (i.e., versions < 3.22) are not as stable and > therefore we do not actively develop for them. Ubuntu is one of the last few > that still support an OS with GTK3.18, but even this will change when Ubuntu > 18.04 LTS is released in a month (it will have GTK3.22). > > Please try using a newer GTK version, preferably GTK3.22.
(In reply to Ansgar Radermacher from comment #4) > I upgraded GTK to 3.22 and it indeed fixed the issue. Thanks for the hint. Any time, thanks for the bug report!
I used to have this exact problem in Eclipse 2018-12 until I updated to Ubuntu 18.04 with GTK 3.22. However, upon updating Eclipse to 2019-09, the problem is back. What could have caused this? I am still on GTK 3.22, Ubuntu 18.04. I tried multiple different theming options within Ubuntu and Eclipse with no success.
(In reply to Ari Fogel from comment #6) > I used to have this exact problem in Eclipse 2018-12 until I updated to > Ubuntu 18.04 with GTK 3.22. > However, upon updating Eclipse to 2019-09, the problem is back. What could > have caused this? > I am still on GTK 3.22, Ubuntu 18.04. I tried multiple different theming > options within Ubuntu and Eclipse with no success. Please try with 4.14 M1, I believe you are experiencing bug 550606 which has since been fixed.
(In reply to Eric Williams from comment #7) > (In reply to Ari Fogel from comment #6) > > I used to have this exact problem in Eclipse 2018-12 until I updated to > > Ubuntu 18.04 with GTK 3.22. > > However, upon updating Eclipse to 2019-09, the problem is back. What could > > have caused this? > > I am still on GTK 3.22, Ubuntu 18.04. I tried multiple different theming > > options within Ubuntu and Eclipse with no success. > > Please try with 4.14 M1, I believe you are experiencing bug 550606 which has > since been fixed. Cannot reproduce in 4.14 M1. Thanks!
