This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 253761 - [81cat] 4k monitor support
Summary: [81cat] 4k monitor support
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: Dev
Hardware: PC All
: P1 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2015-07-24 21:41 UTC by muellermi
Modified: 2017-11-07 16:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (61.63 KB, text/plain)
2015-07-24 21:41 UTC, muellermi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description muellermi 2015-07-24 21:41:54 UTC
Product Version = NetBeans IDE 8.1 Beta (Build 201507231027)
Operating System = Windows 8 version 6.2 running on amd64
Java; VM; Vendor = 1.8.0_51
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.51-b03

NetBeans offers a lot of configuration parameters. For example, the font size for the code editor might be adjusted.
On the other hand, the font size of the project tree is influenced by the OS font size. 
Adjusting at OS level, at NetBeans level, and sometimes nowhere is dissatisfying. Especial on a modern 4k monitor, some parts are hard to use.

Thus, I propose a real zoom: with one input the whole NB IDE zooms in or out, Including all fonts, icons, images etc.
The user may key in the zoom factor or change it by using a slider. I suggest factors from 75% up to 200% (or 250%)
Comment 1 muellermi 2015-07-24 21:41:59 UTC
Created attachment 154869 [details]
IDE log
Comment 2 muellermi 2016-03-10 10:14:40 UTC
Although the user may change the font size in the editor window as well as in other windows, some element gets really small on screens with a high resolution, for example the tree or the icons. The total look and feel becomes ugly. And due to the undersized icons, it becomes hard to use them.
Due to my discussions on JavaLand, a couple of people moaned this. By now, IntellyJ IDE seems to be the only big IDE which can be adopted to higher resolutions. SInce more developers switch to 4K resolution this matter becomes urgent. That's why I increase priority.

Summary: NB offers some features to adopt to the screen resolution, but they mostly affect a single part of the ide, whilst the user needs to tweak other parts separately. Some parts cannot be adopted yet.

--> redesign the icons to be vectorized
--> change all sizes on one click

beside setting the scaling factor as I suggested before, it might be usefull to offer a resize feature by mouse. For example if the user resizes the window whilst pressing a special key (e.g. Ctrl) niot only the size of the window changes but the size of all elements including fonts and icons.
Comment 3 tbrunhoff 2017-09-18 14:11:54 UTC
I've read that fixing this has been put off pending release of jdk9.  I just installed an early access jdk9 and NB dev (Build 201709180002). It doesn't look pretty, and even gets a classNotFound exception (https://netbeans.org/bugzilla/show_bug.cgi?id=271499).

In my case, I have a new dell 7520 15" 4k display (3840x2160) which puts the dpi at about 240. Running the the current jdk8 has many of the visual items at microscopic size. I have the code font set at 30 in order to see it, and the look and feel is set to GTK+. This is barely usable. Is there a workaround such as a config?
Comment 4 blurry 2017-11-07 16:25:04 UTC
I don't get this issue when using Java 9 -- I believe that the root of the issue was Swing not having HiDPI support for any platforms except OSX since Java 7.  I started using daily builds of Netbeans 9 and Java 9 specifically because Java 9 introduces proper HiDPI support.  I suggest that we close this issue as "Won't Fix" with the guidance that affected users install Java 9 and optionally install Java 8 for older code projects that require that runtime as well.  I can't imagine that investing additional effort in a Swing-based GUI is a good use of time compared to, say, porting it over to JavaFX.