https://bugs.kde.org/show_bug.cgi?id=407179
--- Comment #7 from Claudius Ellsel <claudius.ell...@live.de> --- I came up with similar ideas and tried some of them unfortunately with no luck until now. Thanks for the idea to just use another constructor. I tried to change it to KLocalizedString for value altogether and did not really like that given that there are at least currently not always localized Strings for the values. I tried implementing a localizedValue method, but then figured that I first need to tackle the problem of retrieving a KLocalizedString in MemoryEntry somehow. I did not really find useful documentation on that, unfortunately. I might look into it a bit deeper tomorrow, if I get the time. -- You are receiving this mail because: You are watching all bug changes.
