https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #7 from Josef Weidendorfer ---
Ah, I should have closed this bug after Luigi's fix,
which uses the ECM feature.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372643
Luigi Toscano changed:
What|Removed |Added
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #5 from Albert Astals Cid ---
That's the "wrong" patch, ECM has support for that, it's just that marble
people refuse to use ECM because reasons
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #4 from Burkhard Lueck ---
Created attachment 102373
--> https://bugs.kde.org/attachment.cgi?id=102373=edit
patch to load kdcachegrind_qt
copy of
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #3 from Josef Weidendorfer ---
(In reply to Albert Astals Cid from comment #2)
> > qcachegrind (the pure-Qt version of kcachegrind) should just depend on Qt,
> > and no need for it to support translations.
> What
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #2 from Albert Astals Cid ---
> qcachegrind (the pure-Qt version of kcachegrind) should just depend on Qt,
> and no need for it to support translations.
What makes qcachegrind differnet than kcachegrind?
> As said above, I
https://bugs.kde.org/show_bug.cgi?id=372643
--- Comment #1 from Josef Weidendorfer ---
> but this catalog is not loaded into kcachgrind nor into qcachegrind.
Oops. I think that translations in a developer tool such as kcachegrind
often is more confusing than useful,
https://bugs.kde.org/show_bug.cgi?id=372643
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
--
You are