1 (edited by geektrader 2018-05-20 08:41:41)

Topic: FSB Pro looks very broken @ 4k resolution.

FSB Pro seems not to be able to handle 4K resolutions as of now. The only way to run it without issues at this resolution, is to set the HiDPI compatibility (on Windows 10, right click .EXE -> Compatibility tab) to "System" instead of "Application". "Application" would mean that the app will have to deal with the 4k resolution completely on it´s own, and "System" will fake HD resolution to the app and then Windows 10 simply resizes it to 4k, which looks very ugly and blurry. Is there any support for real 4K planned? Here is how it looks if FSB Pro has to deal with the 4k resolution completely on it´s own:


Re: FSB Pro looks very broken @ 4k resolution.

I have no way to test it now. However I'll add your report in my ToDo. There are no immediate plans for fixing it.

Re: FSB Pro looks very broken @ 4k resolution.

Yes, FSB Pro is a mess at 4K :-( The only way is to use the compatibility mode, which makes it look grainy on the other hand. No good solution here as long as Popov doesn´t rework it to support HiDPI.

4 (edited by sleytus 2018-12-21 14:32:30)

Re: FSB Pro looks very broken @ 4k resolution.

HiDPI (High Dots Per Inch) displays are screens with a high resolution in a relatively small format. They are mostly found in high-end laptops and monitors.

This is a Microsoft Windows issue -- actually, a driver issue -- and not related to forex:

FSB-Pro is developed using Microsoft's Visual Studio development environment.  When a Windows application runs it makes calls into .NET Framework which, in turn, call into the Windows OS which, in turn, calls into driver code.  There are software drivers for every device attached to a machine -- including exotic display adapters.  The primary purpose of an OS is to hide nitty-gritty details of the hardware and relieve the developer from having to worry about these details.  Furthermore, there are zillions of different types of hardware and most hardware manufacturers consider their designs to be proprietary.  It is impossible for developers to have to deal with the myriad of hardware configurations out there (however, it wasn't so long ago we did have to).  The modern solution is "software drivers" -- these are usually developed by hardware manufacturers and distributed freely.  When you install Windows it already includes thousands of software drivers for common devices from major manufacturers.  However, for new hardware or hardware from less well-known manufacturers, it is left to the user to manually install the needed (or latest version) software driver.

If the hardware doesn't work properly -- especially a device as common as a printer, or display, or speaker, or network adapter, etc -- it's usually a software driver issue and something an application developer has no control over.  The fact that a "compatibility mode" improves the situation is another clue it is a driver issue.  FSP-Pro knows nothing about "compatibility modes" -- it's the same FSB-Pro code running in both situations.  So -- if compatibility mode makes a difference then that means the behavior is affected by the Windows OS (and the drivers it relies upon).