https://bugs.kde.org/show_bug.cgi?id=514151
--- Comment #6 from Friedrich W. H. Kossebau <[email protected]> --- > With literal "65536", I get the crash. "65535" does not crash. If I return > the value through a function, though, it does not crash - it seems to simply > limit the value to a maximum of 65535 in that case. Okay, so consistent with what I see, starting to have a first working theory for the cause there, let's see... > Even something as simple as an ellipsis "..." would be great. More elaborate > could be "%d more entries (%d bytes) not shown...", or something along those > lines. I can't imagine what else you might add that would be useful in the > general case. Guess ellipsis would be what I can use when doing a fix for this bug report and release still for 0.26, where translators would not like a new UI string to appear. Mentioning the complete missing byte size was not on my plate, seems sensible though and will consider for the development version. Good, thanks again Brendon for your quick replies & input, will see to turn the started work into a proper fix over the next days/weeks. And while I had not planned further releases until the Qt6 port is done ,another intermediate release, showing life, for now should help the spirit, and with this fix might at least make one person more happy :) Would target the date of 2nd of February, by some tradition. Will report back here once I have something worth to test, for anyone who is interested/able to test self-built Okteta versions. -- You are receiving this mail because: You are watching all bug changes.
