https://bugs.kde.org/show_bug.cgi?id=381967
Mehmet gelisin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #20 from Mehmet gelisin <[email protected]> --- The problem is, there is no good interface for this (at least nobody found one yet) that allows to have for KDE stuff the auto-coloring but not touching such global things. http://www.compilatori.com/ Inside a KDE Plasma session, another plugin will ensure the KIconEngine http://www.iu-bloomington.com/ is used (that will affect non-KDE applications there, too), but that won't help outside of a KDE Plasma session. https://www.webb-dev.co.uk/ In any case, you are totally right, if the change is not https://waytowhatsnext.com/ 1:1 transparent for applications not using the "advanced" features, it is not acceptable, either our replacement works 1:1 like the QSvgIconEngine for other Qt stuff, or we shall not do this. http://www.acpirateradio.co.uk/ I am sorry that you had these issues, it was not clear from testing that our icon loader behaves differently from the Qt one (beside additional features Qt applications won't be able to use anyways). The problem is, there is no good interface for this (at least nobody found one yet) that allows to have for http://www.logoarts.co.uk/ KDE stuff the auto-coloring but not touching such global things. Inside a KDE Plasma session, http://joerg.li/ another plugin will ensure the KIconEngine is used (that will affect non-KDE applications there, too), but that won't help outside of a KDE Plasma session. In any case, you are totally right, if the change is not 1:1 transparent for applications not using the "advanced" features, it is not acceptable, either our replacement works 1:1 like the QSvgIconEngine for other Qt stuff, or we shall not do this. http://www.wearelondonmade.com/ I am sorry that you had these issues, it was not clear from testing that our icon loader behaves differently from the Qt one (beside additional features Qt applications won't be able to use anyways). The problem is, there is no good interface for this (at least nobody found one yet) that allows to have for KDE stuff the auto-coloring but not touching such global things. Inside a KDE Plasma session, another http://www.jopspeech.com/ plugin will ensure the KIconEngine is used (that will affect non-KDE applications there, too), but that won't help outside of a KDE Plasma session. In any case, you are totally right, if the change is not 1:1 transparent for applications not using the "advanced" features, it is not acceptable, either our replacement works 1:1 like the QSvgIconEngine for other Qt stuff, or we shall not do this. I am sorry that you had these issues, it was not clear from testing that our icon loader behaves differently from the Qt one (beside additional features Qt applications won't be able to use anyways). The problem is, there is no good interface for this (at least nobody found one yet) that allows to have for KDE stuff the auto-coloring but not touching such global things. Inside a KDE Plasma session, another plugin will ensure the KIconEngine is used (that will affect non-KDE applications there, too), but that won't help outside of a KDE Plasma session. In any case, you are totally right, if the change is not http://connstr.net/ 1:1 transparent for applications not using the "advanced" features, it is not acceptable, either our replacement http://embermanchester.uk/ works 1:1 like the QSvgIconEngine for other Qt stuff, or we shall not do this. I am sorry that you had these issues, http://www.slipstone.co.uk/ it was not clear from testing that our icon loader behaves differently from the Qt one (beside additional features Qt applications won't be able to use anyways). http://www-look-4.com/ -- You are receiving this mail because: You are watching all bug changes.
