Example of a high DPI skin?

from WinCustomize Forums

I'm going a little out of my mind trying to get Windowblinds skins to work without blurring on a high resolution screen, so I have an easy question:

Can someone link to an example of a skin that has high DPI support (preferably a free one)?

I've seen multiple posts saying Windowblinds supports high DPI settings, but I've seen no evidence of this so far.  If I switch to a DPI higher than 100%, the graphics always blur.

Alternately, if you want to post a screenshot of a Windowblinds skin on a high-dpi desktop, that would be helpful too.

Thanks in advance.

windowblinds
11,847 views 11 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues. From what I understand, current version of Windowblinds does support some sections for high DPI but its seem it only work on Windows 7. Not in Windows 10. And, from my understanding, future release of Windowblinds will have better support on high DPI.

Thanks

Basj,

Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Urg, well that clears up my confusion at least.  Is there any rough time projection when Windowblinds will support this?

Galactic Civilizations IV
Reply #3 from Stardock Forums Top

There was a basic announcement of Windowblinds 11 somewhere in 2022-2023.

Thank you.

Basj,

Stardock Community Assistant.

Reply #4 from Stardock Forums Top

Basj is incorrect here.

There is no difference in high dpi support between Windows 7 and Windows 10 in WB.

Reply #5 from WinCustomize Forums Top

Quoting Neil, reply 4

Basj is incorrect here.

There is no difference in high dpi support between Windows 7 and Windows 10 in WB.
End of Neil's quote
I'm not trying to be rude, but please prove it.  What he's saying reflects my experience so far.  Can you post a screenshot of a skin scaling without blurring on Windows 10 with DPI higher than 100%, or name any skin that is high-dpi ready?

If it's a problem on my end, I'll troubleshoot, but I need actual evidence what I'm trying to do is possible.  It will be a lot easier for me to fix the problem if I can find a skin that works properly on Windows 10 with DPI scaling and work backwards from there.

Reply #6 from Stardock Forums Top

I might have a misunderstanding of High DPI usage in Windowblinds. For me, if High DPI graphics available for that part of the skin. It will be use when User change from 100% to higher scaling. This can be test and see on Windows 7, but, not on Windows 10. I made a video to see the difference on Windows 7 vs Windows 10 using a test skin I make specially to show this.

I made a skin-substyle with a single color block for the High DPI portion of the skin and test it on Both Windows 7 and Windows 10 going from 100% to 150%. The video below will show the result.

If I am wrong and misunderstood the concept please clarify.

Thank you.

Basj,

Stardock Community Assistant.

 

 

+1 Loading…
Reply #7 from WinCustomize Forums Top

Quoting basj, reply 6

If I am wrong and misunderstood the concept please clarify.
End of basj's quote
No, you understood 100%.  Thank you for taking the time to make the video.  It's very illustrative and shows the experience I've been having with this.  Either Neil knows a workaround we don't, or else he's mistaken.

I think that is kind of deceptive for Stardock to not make this more explicit when talking about high DPI support however.

Reply #8 from WinCustomize Forums Top

I am also very confused about this.

Here's what WindowBlinds claims:

 

As you can see, I've set an image for 125% scaling. This image is very different from what it should be, it's there just for testing.

Here's what in the corresponding dpi file:

[120]
Image=S3\0frametopuis.tga

(I have no idea why 125% scaling corresponds to 120 value in the file).

 

I'm using Windows 10 Home with 'make everything bigger' set to 125% and as best as I can tell, setting High DPI image has no effect whatsoever. It still uses the base image and stretches it horribly for 125% zoom.

Am I doing something wrong or is this broken for everyone?

Reply #9 from Stardock Forums Top

Quoting meepomorp, reply 7


Quoting basj,
reply 6

If I am wrong and misunderstood the concept please clarify.

No, you understood 100%.  Thank you for taking the time to make the video.  It's very illustrative and shows the experience I've been having with this.  Either Neil knows a workaround we don't, or else he's mistaken.

I think that is kind of deceptive for Stardock to not make this more explicit when talking about high DPI support however.

End of meepomorp's quote

The video isn't showing the same thing.

Those high dpi images are indeed obsolete on newer OSes, but I was talking about per dpi images set on each of the sections in SkinStudio.  There are some changes coming in WB 11 which will simplify the need to provide all the dpis and reduce it to 100% and a higher dpi and scale down the larger one when required.

Reply #10 from Stardock Forums Top

Quoting Solforo, reply 8

I am also very confused about this.

Here's what WindowBlinds claims:



 

As you can see, I've set an image for 125% scaling. This image is very different from what it should be, it's there just for testing.

Here's what in the corresponding dpi file:

[120]
Image=S3\0frametopuis.tga

(I have no idea why 125% scaling corresponds to 120 value in the file).

 

I'm using Windows 10 Home with 'make everything bigger' set to 125% and as best as I can tell, setting High DPI image has no effect whatsoever. It still uses the base image and stretches it horribly for 125% zoom.

Am I doing something wrong or is this broken for everyone?
End of Solforo's quote

There seems to be a bug in what skinstudio is writing to the .dpi file.

If you go into the skin directory and find the frametopuis.tga.dpi file you should edit it to remove the S3\ part of the path under the [120] section.  So just have the filename.  This will then work correctly.

Sorry about this, it seems nobody has ever reported this before so it went unnoticed.

Reply #11 from WinCustomize Forums Top

Quoting Neil, reply 10

If you go into the skin directory and find the frametopuis.tga.dpi file you should edit it to remove the S3\ part of the path under the [120] section. So just have the filename. This will then work correctly.
End of Neil's quote

Wow, thank you very much!

This is indeed the case, with this workaround I should be able to get sharp controls @ 125% zoom!