So, I have Xplorer² set with a nice color coding for files that are both System and Hidden (to make me hyper aware of files that should not be deleted). (I picked a very garish yellow font on black background extending across all columns - yeah, not accidentally deleting these files lol).
However, it has had an unforeseen consequence - which may have alerted me to a bug.
If I view my C: drive, which has several of these types of +HS files / folders, I see something very, very odd.
If I use the [CTRL] + [Plus key] to auto size all columns, the size column actually truncates the last 2-3 digits for files that are in the GB range. I've checked on other folders, and it does not happen there on GB sized file - only on the C: drive.
See the attached screenshots.
1) Normal folder with GB sized content, no auto-sizing.
https://photos.app.goo.gl/uwyv39SqcXVtKPL92
2) Same folder after auto-sizing:
https://photos.app.goo.gl/aPhSwc3cQ48NqxLF3
3) C drive without auto sizing:
https://photos.app.goo.gl/E1VmJzwaNUmQbejY6
4) C drive after auto-sizing:
https://photos.app.goo.gl/qUZB2GrbCr17imD93
During the whole process of making these screenshots, I noticed that it only occurred on the files where I have the custom color coding. That led me to digging around, and I think I may have a suspect here.
Here are the settings for the custom color coding:
https://photos.app.goo.gl/VqFzpU5heeyP0h6y1
Is that the cause right there for this 'issue' - my use of a bold face font for the color coding only?
Possible bug?
Moderators: fgagnon, nikos, Site Mods
- FrizzleFry
- Platinum Member
- Posts: 1241
- Joined: 2005 Oct 16, 19:09
Re: Possible bug?
I think I have noticed this before when using bold for color coding. It seems Nikos is using the unbolded file/folder names to determine the pixel size for autosizing.
Re: Possible bug?
strictly speaking it's a bug with the system listview control under custom drawing.
Re: Possible bug?
Thanks for the confirmation, ff, and the technical explanation Niko.
When I first saw the 'bug' was a couple of hours before I completed my post here, which is how I discovered the possible source.
Luckily, that garish color scheme works well enough that I do not need to actually use the bold font typeface in it (it is actually a modification of the original color scheme which was much nicer to look at, but didn't provide me with enough emphasis on +HS files, such as desktop.ini, so that I could easily manipulate them manually whenever I need). I'll just kill it.
When I first saw the 'bug' was a couple of hours before I completed my post here, which is how I discovered the possible source.
Luckily, that garish color scheme works well enough that I do not need to actually use the bold font typeface in it (it is actually a modification of the original color scheme which was much nicer to look at, but didn't provide me with enough emphasis on +HS files, such as desktop.ini, so that I could easily manipulate them manually whenever I need). I'll just kill it.