I use a 4k monitor in the resolution 3840 x 2160 but with a scaling of 175% because at 100% everything is too small for me.
There are no problems with almost all applications and the writing is well readable due to the scaling.
Except the SqlDeveloper... all fonts seem to be blurred somehow. You can read them but somehow it is annoying.
I'm using Windows 11 by the way.
I've been through the google jungle myself and here's what I've tried:
followed this guide: https://www.thatjeffsmith.com/archive/2019/09/fixing-the-my-sql-developer-ui-is-so-tiny-problem/
SqlDeveloper updated to 22.2.0
downloaded jdk-17.0.4 and added it to product.conf SetJavaHome C:\Program Files\Java\jdk-17.0.4
tried the same with jdk-18.0.2 (dont ask me why i thougth this will change anything...)
sql developer => right click => properties => compatibility => override high dpi settings to Application
Google is full of solutions regarding the jdk and dpi settings but that's all I can find and it doesn't seem to work for me.
Changing the font size in SqlDeveloper is also not a solution for me because the size is already ok and that does not fix the blurriness.
So i hope there is someone out there who already fought that problem.
Found your questions from google... At the end I gave up and just use DBeaver instead
Related
So we've recently had our dev machines replaced with 4k laptops and windows 10. I've got visual studio set up, the DPI scaling has worked for the most part to make things usable. The only problem is errors / dialog boxes.
I can't find a way to make them scale up to something readable. Instead I'm getting unintelligable errors written for ants.
Has anyone had any experience of this issue on high DPI screens? And if so did you find a way to fix the problem?
As an example of what I'm talking about, content is scaled, but the options to the left are not. If I get an error popup (exceptions, build failed etc) then everything is in that tiny text, making it unreadable.
I remember having fixed this by finding a value in the registry that appeared to be overriding the how the images were shown, but I can't remember where it was, nor the source that showed me. I'm getting annoyed again at having images such as these show up when I pin them to my Windows 10 Pro Start Menu:
I know that there was a fix for this, but for the life of me, I can't seem to remember what it was.
As a note, I had tried tweaking with the shortcuts found in C:\Users[me]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Chrome Apps
to no avail. I swear the fix was related to something simple in the registry, but I can't place my mind on what it was. Any suggestions?
I am encountering an issue I have never seen before. During development of a new website, while testing on mobile I noticed my images are getting resized and compressed. An image that is normally 1600 by 600 naturally, is being resized and compressed to 375 by 140 this is then displayed as the natural size.
I have an older copy of the website with the same images. The issue does not occur with those.I have not implemented any server side caching yet.
Is anyone familiar with this issue? I haven't been able to find any information on it. I looked up 'Image compression bug on chrome', 'chrome resizing images', and at least a dozen other queries, but nothing that seemed to match my issue. Other colleagues are seeing the same issue on their own devices as well.
Nevermind. It turns out one of my colleagues in the past had run a small experiment with cookies and limiting the image widths, and had left it there.
My team has used the same Install Shield 12 project for years. Several weeks ago Windows Explorer in Vista and Win7 stopped displaying icon sizes above 16x16 for the installer. So List, Details, and Small views show the 16x icon but Tile, Thumbnail, Medium and Large views are just text.
This is true for new installers, but also for 3 years of archived installers. We have not tried systems older than Vista, but we have tried it on multiple machines. We use a normal 32x32 32bit ICO file. In IrfanView it has two pages with a blank first page. In InstallShield it has one Icon to choose from at index 0. None of this has changed in the last three years.
I've dug around on the Flexera forums, here, and in various Google results but I haven't discovered anything except that quite a few people still use Install Shield 12.
Does anyone know what happened or how to fix it?
I suspect that there has been a recent windows update that changed the rules. Do we need to include an ICO containing different sizes? Does windows now restrict something that the older versions of Install Shield does?
I changed tactics. Instead of trying to understand why our old ICO suddenly stopped working I just created a new ICO. I made an effort to create exactly what Windows would expect in an ICO.
A quick and dirty search for application icon editors turned up IcoFX (this link goes to an free older version). Even Stack Overflow contributors recommended it. I fed it a pristine 256x256 png and told it to "Create Windows Icon From Image" using its default settings:
- 4bit # 16x16, 32x32
- 8bit # 16x16, 32x32, 48x48
- 32bit # 16x16, 32x32, 48x48, 256x256
This new ICO worked, although I had to rebuild my Windows icon cache to see the change.
I'm disappointed that I don't know what changed in the OSes. However, this solved the problem and also dramatically improved our old 32x32 pixel by 32bit ICO.
I just loaded a new system and everything looked fine. Then all of the sudden Chrome starting displaying certain fonts on certain web pages with what looks like no anti-aliasing. I've had this happen before on another system as well. Same thing, everything looked fine and then all of the sudden this started. Any ideas or suggestions? Thanks.
Screenshot of what I'm typically seeing.
http://www.denkers.com/test/font.jpg
First, make sure your text encoding is correctly set to Unicode (UTF-8) by going to the wrench icon -> Tools -> Encoding
If that doesn't work, go to the wrench -> About Google Chrome and update to the latest version.
Finally, if none of these work, try reinstalling Google Chrome.