Double commander high dpi windows#

The scale factor is expressed as a floating point number, for example 1.0 or 2.0, or informally as 1x and 2x.įor example, creating a QWindow or QWidget, and setting its size to 200x200 will cover 200x200 display pixels on a normal density display (with a device pixel ratio of 1.0), but will cover 400x400 pixels on a high density display (with a device pixel ratio of 2.0). The application operates in device-independent pixels, which are then mapped to the physical pixels of the display via a scale factor, known as the device pixel ratio. Qt uses a model where the application coordinate system is independent of the display device resolution. Lower-level graphics drawing (such as OpenGL code) need to be high-DPI aware, but can use cross platform Qt APIs to learn about the platform's display resolutions. Changes in the platform's user preferences are automatically picked up. Qt will automatically account for the display resolution when using higher level APIs such as Qt Widgets and Qt Quick, and applications only need to provide high-resolution assets, such as images and icons. Qt supports high-DPI displays on all platforms, and provides a unified API that abstracts over any platform differences. The increased resolution is used to provide more detailed content on screen (smoother text, more detailed icons), rather than more content (more windows, larger window sizes). If any of these doesn't give the expected behavior, please post a screenshot.High-DPI displays – also known as retina displays – are displays with high resolution (pixels) in relation to their physical size (mm), resulting in a high pixel density, or high number of dots per inch (DPI).

In Tools->Tool Properties select General / Appearance / Fonts and change the font for Text Editors to the Monospaced font. The following is applicable for both HiDPI and non HiDPI monitors. If you after restart need to adjust the font sizes even further, open Tools->Tool Properties and the General / Appearance / Fonts.

Double commander high dpi windows#

Change Font Scale to the same resolution that is set in Windows and restart. To change the resolution in DbVisualizer click the General / Appearance / Fonts category. The setting will force the resolution for Java to 100% and ignore any higher resolution defined in Windows. In Tools->Tool Properties and in the General category insert the following on a new line in Java VM Properties: =1 Choosing System (Enhanced) seems to be a little better. Choose System for Scaling performed by.Check Override high DPI scaling behavior.Find java.exe you use, or the dbvis.exe file if using the launcher in Windows File Explorer.Hopefully a future Java 9 release will fix it, but for now there are several workarounds:ĭo as follows if you are experiencing the problem with a HiDPI monitor: The problem is in Java 9 and visible both with non HiDPI and HiDPI monitors. Unfortunately we have found that Java 9 causes an issue in the editor where the insertion point (caret) doesn't align with where the mouse cursor is clicked. Java 9 is included starting with DbVisualizer 10.0.8 for the first time, with support for HiDPI displays. The following is from the solution article:

This happened immediately after upgrading to 10.0.8 and has persisted for a week and several reboots.

One thing I do that many don't is keep my Windows taskbar on the left side instead of the bottom, in case that made it resize. I have tried changing my theme, did not notice a difference. I am on Windows 7, the same as all my coworkers, who have not had any issues. * Just under the title bar, I can see a one-pixel row which is from the last window I alt-tabbed to - the open tabs in Firefox, or a black line if I was in Putty. * 'drop shadows' behind tabs, like they have a double border * bad aliasing on icons, especially the > Other graphical artifacts you may be able to see in the screenshot: For example, in the screenshot below, I clicked to the right of the period and dragged left over the word 'aliqua', but text selected and copied to the clipboard is '. The result of this is that when I click and drag on SQL Commander text, the actual selection area begins several characters to the right of where my mouse clicked. The most severe problem is that SQL Commander's font display size appears to be different from the actual text size. Immediately after upgrading to 10.0.8, I have had a host of graphical issues with DBVisualizer.