https://bugs.kde.org/show_bug.cgi?id=498820
--- Comment #6 from John <[email protected]> --- (In reply to Thomas Bertels from comment #5) > Created attachment 196993 [details] > Sizes as shown in Windows Explorer > > Rather than adding a setting to choose the number of decimals, I think it > would better to add a second Size column (hidden by default), with unit set > to KB like in Windows Explorer. > > This would: > - Let former Windows users keep the size displayed as they're used to > - Achieve maximal meaningful precision (bytes not being shown) > - Be simpler to implement and use than adding a new setting for the precision > - Let users display the size differently depending on the folder > - Let users quickly compare items sizes without looking at the unit I don't think that would work for big files like in the 20-70 GiB and even more as they have too many KBs (KiBs) to display. I think that could make the column way too large. In case you're wondering what kind of files could be 20-7 or even more, here are a few examples that I already bumped into: 4K + HDR at high bitrate MKV files. Games ISO files. Hard disk backup files. Archive files containing a big amount of folders and files. I created a backup one of more than 700 GiB. Otherwise, copying many folders and files from one hard drive to another or to a USB pendrive could take way too long. And his insufficient file or folder size precision doesn't affect only the content view column. A lot of time I find myself working with two windows side side by side and right clicking on items with identical names to see if they are duplicates. If I look just the at shortened number, I cannot figure out if they are the same or not, so I have to compared all the bytes in the parentheses. I'm tired of how many times I've seen the first number after the coma being the same, just to see that after I compare everything in the parentheses they are different and the folders or files are indeed different. I bet this would happen much less if the Folder or file properties window also had more precision that just one digit after the floating point. I still think the configurable size accuracy would be the best with the 2 or 3 digits after the floating point by default. So strange to see that even Windows has better accuracy and not with 2 digits, but with 3, which is even better. -- You are receiving this mail because: You are watching all bug changes.
