https://bugs.kde.org/show_bug.cgi?id=430046
medin <med.medin.2...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|INTENTIONAL |---
Status|RESOLVED |REOPENED
--- Comment #3 from medin <med.medin.2...@gmail.com> ---
(In reply to Nate Graham from comment #2)
> Yea I'm afraid this feature was removed in Plasma 5.20 as it was impossible
> to make it work correctly due to unfixable deficiencies in GTK2. Any app
> still using GTK2 at this point ought to be ashamed of itself; GTK2 has been
> unmaintained for years and GTK4 is about to be released. Go bug the
> developers to be responsible and port their apps to a more modern toolkit. :)
But it was working fine before 5.20, and many useful GTK2 apps are still useful
and have no GTK3 or Qt alternative and will never ported to new GTK3+ versions,
so demanding many old apps (whose some maintainers are already dead) to be
upgraded to match plasma logic seems to be far away from reasonable. I use some
old GTK2 apps that weren't maintained for many years and they still work fine
and do the work perfectly.
At least in 5.19 there was options for GTK2 and GTK3 themes, if GTK2 has some
problems why not let the option for the user to choose GTK2 theme manually
instead of removing it and break theme selection for all those old useful apps
?
Some platform (like JDK and Python) are still supporting GUI apps that were
written for more than 20 years and they still work fine, so why Plasma choose
to remove existing working solution and break other apps ?
--
You are receiving this mail because:
You are watching all bug changes.
