Summary: | SWT GTK3 doesn't render tables with GTK3 Theme "oxygen-gtk" | ||
---|---|---|---|
Product: | [Plasma] Oxygen | Reporter: | Andrey Loskutov <loskutov> |
Component: | gtk3-engine | Assignee: | Hugo Pereira Da Costa <hugo.pereira.da.costa> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | b7.10110111, hugo.pereira.da.costa, rdieter, web |
Priority: | NOR | ||
Version: | 4.13.2 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
URL: | https://bugs.eclipse.org/bugs/attachment.cgi?id=242039 | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
eclipse tables with adwaita theme (OK)
eclipse tables with oxygen-gtk theme (EMPTY!) |
Description
Andrey Loskutov
2014-12-29 20:12:59 UTC
Created attachment 90160 [details]
eclipse tables with adwaita theme (OK)
*** This bug has been marked as a duplicate of bug 340288 *** Created attachment 90161 [details]
eclipse tables with oxygen-gtk theme (EMPTY!)
I've added two screenshots to demonstrate the issue. I can help with testing if needed.
@Hugo I don't think this one is a duplicate. The theme is loaded and almost works. @Andrey what if you set OXYGEN_DISABLE_INNER_SHADOWS_HACK=1 environment variable before running eclipse? Ruslan, you are genius! This helps!!! Thanks! Any technical hints why this needed and what the best way for Eclipse to deal with this? Should we fix Eclipse launcher to always set this variable, I guess this should not affect any other themes? Or is there a more elegant solution possible? @Ruslan I agree. However, I do not see much point in fixing issue for a code that will become dead and useless the next time gtk3 is updated ... Hence the 'duplicate'. Now of course, if there is an easy fix prior to this programmed death ... @Andrey Actually, I do agree with Hugo on the uselessness of our trying to fix this on oxygen-gtk3 side. Starting form GTK 3.15, theme engines won't be loaded at all, and oxygen-gtk3 will be dead, as you may have read in the bug which this one is marked a duplicate of. So, either wait until GTK 3.15 is widespread, so that the bug would be invalidated, or temporarily set this variable for the launcher. > Any technical hints why this needed
This is because of how some (non-)GTK apps like Eclipse interact with our (rather intrusive) hacks. These apps aren't true GTK, thus the incompatibility. I just know this symptom, that's why it was the first thing to suggest.
Anyway, thanks guys! I will try to patch Eclipse then. I really appreciate your work and it is really sad what happens with GTK/Gnome in the last few years. They seem to live in a parallel universe with only brain dead users eagerly waiting for the next removed feature. But this is going too much offtopic. Just for the record, the proposed patch for Eclipse is: https://git.eclipse.org/r/38843 |