When opening MuseScore the zoom level is not correct

• Nov 19, 2015 - 21:51
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

d76e51d276

* Launch nightly, doing a factory reset to be sure.
* Close the Start Center and My First Score is visible, but shrunk.
* Zoom level says 100%
* Click on the down-arrow beside the 100% zoom and the score will resize.

See https://musescore.org/en/node/87861#comment-387961

Comments

• Dec 13, 2015 - 11:02
Status (old) closed ⇒ active

MS Nightly 12 Dec 2015 (77e980d) / Win 7

This issue is still there in the latest nightly. At 100% magnification scores look about 75% of the size in MS 2.0.2. (It was ok in this nightly – d45cc19)

Reply

• Dec 13, 2015 - 16:11

Yes, I believe so. Should work well on all but high DPI Windows 7 systems once those changes are merged. On high DPI Windows 7 systems, resolution will still be off because we don't know how to get an accurate read. But the vast majority of systems that old don't have high DPI displays.

To be clear, this is a slightly different issue than the one reported here - currently there is no shift as cescribied in the original report. But it it's still off for certain systems; it just *stays* off.

Reply

• Dec 13, 2015 - 21:36

Hmm, actually, score size should *already* be correct on all but high DPI Windows 7 systems. It's other UI elements that my PR fixes. geetar, are you using a high DPI display (>100 DPI>? If so, unfortunately we still don't know of a fix for Windows 7 systems, but uograding to Windows 8 or later would allow it to work correctly.

Reply

• Dec 13, 2015 - 21:49

Nope, without that PS on Windows 7 an A4 score at 100% is about 15 cm wide, instead of the real 21. With your PR it is almost correct, some 20cm, I don't recall exactly, but I'm pretty sure I tried the code from that PR.

Reply

• Dec 14, 2015 - 11:13

Oh, on all but high DPI Windows 7 systems, that is true, I've just tried once again. But also with that patch is looks exactly like 2.0.2 and not some 25% smaller

And yes, my 'high res' monitor is set to that 96DPI too, but actually is has some 132DPI (so should get set to 137%), while my 'low-res' screen has some 101DPI (so should get set to105%). So in that dialog even Windows itself gets it wrong and claims 100% to be 96DPI

Reply

• Dec 14, 2015 - 15:45

*True* (physical) DPI is not a setting you make in Windows - it's an inherent attribute of your monitor. How many pixels it has divided by how many inches it is - very literally dots per inch, which is what DPI stands for. The Windows setting allows you to tell Windows what resolution you'd like it to *pretend* the monitor is, which I suppose might also have some relevance here, but isn't what I'm talking about. It's monitors with a *true* (physical) DPI - the actual numebr of pixels divided by the actual number of inches - that is greater than 100 that will show problems in Windows 7 (only).

But I had forgotten, since Windows 7 reports the physical DPI as 72 even for normal monitors, you would indeed see the wrong score size on that OS only regardless of your monitor and my PR does indeed contain a hack that corrects this for non-high-DPI monitors.

Reply

• Dec 14, 2015 - 18:26

"since Windows 7 reports the physical DPI as 72 even for normal monitors"

I've seen this number 72 quoted a lot lately, but I've seen very little evidence for it. In my experience, Windows uses 96 DPI as the default. Where do you see or find this value 72?

If you launch a CMD prompt and type

wmic desktopmonitor get pixelsperxlogicalinch

I always see 96 returned.

Reply

• Dec 14, 2015 - 20:06

72 is the value returned by the Qt function physicalDotsPerInch() on Windows 7 systems. Not sure what low level function is being called internally or if the issue is really.with Qt or Microsoft. But again, I think that 96 number is something different - a "logical" value you can use to trick the system into scaling things differently.

Reply

• Jan 4, 2016 - 16:28

I expect it will still show scores too small on Windows 7 & earlier systems that are running with a high DPI display. I don't know of a way to get Qt to report meaningful DPI figures in these cases. But I suspect the scaling was off similarly in previous releases as well, so hopefully it won't appear to be a regression.

Reply