Possible high DPI text crispness issue in 1.5?

Discussion related to "Everything" 1.5 Alpha.
Post Reply
JTCGiants56
Posts: 192
Joined: Fri Nov 28, 2014 3:58 pm

Possible high DPI text crispness issue in 1.5?

Post by JTCGiants56 »

I use high DPI 4k in windows and i'm not sure if 1.5 is rendering text with high DPI support with the same crispness than 1.4 does. I didn't notice this in 1.5 until now so it's possible this was introduced in the last couple updates (I installed but didn't really use the last few builds).

See below - Top is 1.5.0.271a and bottom is 1.4.1.
21212.JPG
21212.JPG (140.66 KiB) Viewed 8099 times
void
Developer
Posts: 15663
Joined: Fri Oct 16, 2009 11:31 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by void »

Thank you for your post JTCGiants56,

It's a bug with the recent Everything 1.5 alpha.

Looks like Everything is rendering the result list text twice.
This is causing the text to look 'thicker'.

I am working on a fix..
JTCGiants56
Posts: 192
Joined: Fri Nov 28, 2014 3:58 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by JTCGiants56 »

Great, you're welcome.
JTCGiants56
Posts: 192
Joined: Fri Nov 28, 2014 3:58 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by JTCGiants56 »

Quick unrelated question since I don't want to spam the threads list - Would the "Content Created" property encompass the below "Media Created" attribute in the below video example? "Media Created" is not listed as an option within Properties.

32323.JPG
32323.JPG (27.91 KiB) Viewed 8093 times
void
Developer
Posts: 15663
Joined: Fri Oct 16, 2009 11:31 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by void »

The internal metadata name for "Media Created" in Windows is date encoded.

Everything just calls it Date Encoded.
I will consider renaming Date Encoded to Media Created to match Windows.

"Content Created" is used on documents. (it maps to System.Document.DateCreated)
JTCGiants56
Posts: 192
Joined: Fri Nov 28, 2014 3:58 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by JTCGiants56 »

void wrote: Sun Aug 08, 2021 1:36 am The internal metadata name for "Media Created" in Windows is date encoded.

Everything just calls it Date Encoded.
I will consider renaming Date Encoded to Media Created to match Windows.

"Content Created" is used on documents. (it maps System.Document.DateCreated)
Thank you, that's great. I think it might be easier for people if the Windows Properties name was used in all cases instead of the metadata name as such in this case there wasn't really a way for me to match the two and search the correct property in everything (unless of course you are aware of the internal metadata names).
void
Developer
Posts: 15663
Joined: Fri Oct 16, 2009 11:31 pm

Re: Possible high DPI text crispness issue in 1.5?

Post by void »

Everything 1.5.0.1272a fixes an issue with rendering text.

Everything 1.5.0.1272a will now use the property name Media Created for System.Media.DateEncoded to match Windows.
Post Reply