Tiny visual glitch in IP Raw View tab

[grindax]

In the metadata section, when a text file is selected (note the pixels under the 'Sy' and 'D'):

raw_view.png (6.09 KiB) Viewed 226 times

Font: Tahoma 8.25

[grindax]

Same thing also happens with text files of type 'System Default (1252)-Unix'. The extra pixels are just in a slightly different place.

[Twisten]

Cool free pixels.
But seriously this is weird, maybe a drawing error that leaves those behind or these are the only visible part of a hidden object/s ?

[Borut]

I am reusing this thread for another tiny visual glitch... Steps to reproduce:

1. Configuration | Colors&Styles | Borders ... Dark border (2 pixel)
2. Hint: No themes here!
3. In the list, click on any column header to sort the column

You will notice that - after releasing the button - a part of the border of a depressed heading persists:

[admin]

Cool free pixels.
But seriously this is weird, maybe a drawing error that leaves those behind or these are the only visible part of a hidden object/s ?

Yes, the caption became too long, and the label is too high, so parts of the wrapped caption are visible.

Fix comes.

[admin]

I am reusing this thread for another tiny visual glitch... Steps to reproduce:

1. Configuration | Colors&Styles | Borders ... Dark border (2 pixel)
2. Hint: No themes here!
3. In the list, click on any column header to sort the column

You will notice that - after releasing the button - a part of the border of a depressed heading persists:

Yes, confirmed and fixed.

[grindax]

Yes, the caption became too long, and the label is too high, so parts of the wrapped caption are visible.

Fix comes.

Unfortunately the fix in 0313 is to simply have it say 'Ascii file'. Before it was possible to know whether it was a Unix text file or not.

Perhaps have it say 'DOS/Windows text file' or 'UNIX text file' instead?

[admin]

You mean info about the line feeds? Yes, I removed it because it was too long. OTOH I might make the metadata pane a bit wider... hmm...

[Twisten]

Oh, yeah its very useful to know if the file is unix/dos/mac or 'undetermined' (for mixed line ending, usually from a botched conversion).
Also it might be useful to have a writefile() option to select the proper encoding.

[admin]

I changed it back in v10.80.0314.