Unusual behavior of text in a frame
- Snip 1 shows the title box with the entire text field highlighted. This highlighting was obtained by sweeping the insertion point from left to right, extreme to extreme. Note that the box is centered in the frame; however, the text is not centered in the box.
- Snip 2 further illustrates the off-centering of the text. This picture was obtained by pressing the End key to move the insertion to the extreme right in the text box.
- Snip 3 illustrates the effect of pressing the Backspace key one time. Notice that (a) the text box narrowed by the equivalent of one text character; (b) the insertion point remained at the extreme right of the text box; and (c) the right-most character was deleted. This is bizarre behavior.
- Snip 4 further illustrates the effect of pressing the Backspace key one more time. The same results were obtained as noted for Snip 3.
I first encountered this behavior when I opened a score in MuseScore 3 that was created in the latest version of MuseScore 2. My initial conclusion was that the aberrant behavior was a a result of the upgrade. However, experimentation revealed that the problem manifested itself on new MuseScore 3 scores, too.
My set-up is as follows, having used your tool in the Help, About menu:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.2.3.7635, revision: d2d863f
The same behavior described above exists in other frames. If I create a new frame (i.e., one not presented as an initial new-score text frame), the aberrant behavior occurs.
| Attachment | Size |
|---|---|
| Snip 1.png | 7.95 KB |
| Snip 2.png | 7.69 KB |
| Snip 3.png | 7.21 KB |
| Snip 4.png | 7.08 KB |
Comments
Apparently the score was filled with 2.1;
As Marc said it seems to be a solved problem. I don't notice the problem on this 32 bit Mint:
Does the PC keyboard have an 'Ins' key active? Or other problem related to the settings?
In reply to Apparently the score was… by Shoichi
Within the hour, I posted the problem in Support with the title "Unusual behavior of text in a frame." I furnished further explanation along with supporting snips. As for the keyboard, I use an external, wireless keyboard connected to my laptop. Also, I do not use the Insert key for any of these operations.
In reply to Within the hour, I posted… by Lawrence Iverson
Do you notice the same behavior in the attached file above?
In reply to Do you notice the same… by Shoichi
Yes. I've attached a snip of what I see.
In reply to Within the hour, I posted… by Lawrence Iverson
Everything you describe about your system, including the wireless keyboard, applies to me as well. I don't get the results you are reporting using your score you attached in the issue report or in a new score. There must be something else going on I'm missing or you are not mentioning.
If I add spaces to the end of the title I see the extra space at the end of the title.
Can you attach the specific score you used for these screenshots? From the looks of it, the only thing I can think is that the font you are using for the text has incorrect metrics.
Oh wait, something else I thought of - a few people have reported odd effects along these lines when starting running MuseScore on multiple monitors with different resolutions at once, that sort of thing. Is that by chance going on here?
In reply to Can you attach the specific… by Marc Sabatella
Sure thing. I've attached it. It is the default/start-up score that appears when I start MuseScore 3. I did not tinker with fonts or anything else.
In reply to Sure thing. I've attached it… by Lawrence Iverson
It seems to be behaving as it should.
In reply to Can you attach the specific… by Marc Sabatella
Oh wait (too). I forgot: I do use a monitor connected to the laptop. The laptop is set for 1920 by 1080. The external VGA monitor is set for 1680 by 1050. However, these are the same settings as for when I use MuseScore 2. My problem appeared only when I upgraded and tried to start using MuseScore 3 on new work or when opening a score created previously in MuseScore 3.
In reply to Oh wait (too). I forgot: I… by Lawrence Iverson
To me (but I'm not a technician) the monitor looks innocent. I don't think it can interfere with text formatting (for example of a document).
You could try https://musescore.org/en/handbook/3/revert-factory-settings
But I don't think it would solve.
In reply to Oh wait (too). I forgot: I… by Lawrence Iverson
Oh Wait (again): Update: I moved MuseScore 3 to the laptop's screen. The problem went away.
The reason I use an external monitor is that it has a larger screen—it's easier on the eyes. Can't MuseScore 3 be made to behave like MuseScore 2 when it comes to rendering text in text boxes?
In reply to Oh Wait (again): Update: I… by Lawrence Iverson
-monitor-resolution DPI?
https://musescore.org/en/handbook/3/command-line-options
In reply to -monitor-resolution DPI?… by Shoichi
The HP w2007's recommended setting is 1680 by 1050 60Hz. And, that is the current setting.
What is the significance of the link you furnished? I looked it over; however, I couldn't see what I could do with it.
In reply to The HP w2007's recommended… by Lawrence Iverson
Calculate the dpi you want to use for the monitor so it's the same as for the laptop and add -D dpi to the end of the command line used to run MuseScore.
In reply to Calculate the dpi you want… by mike320
Presumably, the syntax would be as follows:
musescore3.exe -D ???
I don't know the method for quoting the DPI. My monitor's recommended setting is 1680 by 1050. (Apparently, that's its best figure.) How does one convert that to a DPI figure that's expected by this option specification?
Question: if I stipulate in the command prompt a DPI figure for the monitor that matches the laptop's higher resolution, what effect should I expect? Remember, the monitor's resolution isn't as high as the laptop's.
Alternatively, and noting that the laptop's recommended setting is 1920 by 1080, I did try using Windows' Display setting screen to change the laptop's setting to match the monitor (i.e., 1920 by 1080 down to 1680 by 1050). I moved MuseScore 3 back to the monitor, exited, then started it again. It came up on the monitor. However, when I clicked on the text box, it behaved the same way. That is, with both screens set for the same 1680 by 1050 resolution.
It seems to me that the new and improved version of the application ought to behave, in this respect, like its predecessor. That is, having to start through the command prompt is not an upgrade.
In reply to Presumably, the syntax would… by Lawrence Iverson
To get the final dpi, you need the diagonal length of the screen. Get the square root of the length squared + the width squared, then divide by the diagonal of the screen. This is the DPI. So I would use 1998 / the laptop's screen diagonal size. This way the laptop's built in screen size stays the same and they both have the same dpi settings.
The problem with the display is the library MuseScore uses doesn't work like it did in previous versions. It is technically a MuseScore problem, but the problem was introduced by the GUI library that allows MuseScore to work on several operating systems.
In reply to Presumably, the syntax would… by Lawrence Iverson
To be clear: this is indeed a bug, but it's not clear where it comes from (could well be in the Qt library framework we use to learn the screen resolution - we're using a newer version of that). So the need to the -D is just a workaround for now until we understand better and can fix the problem on our end.
Meanwhile, the resolution is often available from your OS in settings somewhere, probably also listed in the information that came with the monitor. Or, as mentioned, just divide the number of dots by the number of inches - that's literally what DPI is.
In reply to Presumably, the syntax would… by Lawrence Iverson
Good old Pythagoras: a² + b² = c²
You have a and b in pixels so can calculate c in pixels. You have c in inch, so you can calulate pixels (Dots) Per Inch. Pretty simple math.
In reply to Presumably, the syntax would… by Lawrence Iverson
You have two of the three most necessary numbers.
now you need a diagonal inch of your monitor (let's say it's 15)
sqrt( sqr(1680) + sqr(1050) ) / 15 = 132
musescore3.exe -D 132
see in attached animated gifs (easy calc.):
ppi is for 1680 x 1050 and 15 inches.
ppi2 is for 1920 x 1080 and 22 inches.
In reply to You have two of the three… by Ziya Mete Demircan
Thanks to all. Those two .gif links are neat. The math is simple enough. I've just never had to use the -D option and to derive the -D parameter before. Finally, I am happy to hear that there is nothing wrong with my set-up. I look forward to having the bug addressed in future release.
Over and out.
In reply to Thanks to all. Those two … by Lawrence Iverson
Well, I tried; however, the recommendations didn't work.
Here's what I did:
1. My external monitor has a 20-inch diagonal screen, with 1680 by 1050 DPI figures. Therefore, sqrt(sqr(1680) + sqr(1050))/20 = 99.
2. Initial conditions: (a) I want to use this monitor to run MuseScore 3; (2) I am assuming that the command prompt entry cited in prior messages, and which is stated below, is intended to be used to start MuseScore3 on the external monitor.
3. Having found musescore3.exe in the BIN directory in the MuseScore 3 directory and changing the directory to the BIN directory, as a test I entered musescore3.exe at the prompt without any other command modifiers. MuseScore 3 started. Yippee! Note that I had the command prompt window running on the monitor's screen. The command looked like this: c:\program files\Musescore 3\bin>musescore3.exe.
4. Then I entered musescore3.exe -D99. Musescore 3 started. However, the same text problem originally cited at the beginning of this thread manifested itself again. That command did not correct the problem.
5. Then I tried putting a space between the -D and 99 (i.e., musescore3.exe -D 99). I got the same result.
Am I missing something here? Is my syntax wrong? I still don't know whether the command in step 4 or 5 is correct.
Again, I have a laptop with a 15-inch diagonal screen with DPI figures of 1920 by 1080. I am connected via a VGA connection to an external 20-inch diagonal monitor with DPI figures of 1680 by 1050. I want to start up MuseScore 3 so that it runs initially and thereafter on the external monitor.
Please advise.
In reply to Well, I tried; however, the… by Lawrence Iverson
your laptop's screen : 146.86
your external monitor : 99
What does Windows recognize your external monitor?
Does Windows know the resolution settings of that monitor?
Right click on musescore shortcut on your desktop, click to "properties" option.
And enter your parameters here.
(this is my settings for 1920x 1080; 22.6 )
Maybe the solution to your problem is not related to DPI settings :)
In reply to your laptop's screen : 146… by Ziya Mete Demircan
To answer your first question, Windows Settings,Display recognizes the external monitor correctly—1680 x 1050.
I did right click on the desktop icon and obtained the same screen illustrated above. However, there was no options qualifier stated. So, I made sure Musescore 3 was closed, then I added -D 99.06 to the Target field. Then I started MuseScore 3 by clicking on its icon. Same problem.
Perhaps you're right. We're chasing the wrong solution. I don't know.
In reply to To answer your first… by Lawrence Iverson
I just tried something else, which resulted in the expected and correct behavior for text boxes. It has to do with a setting in the laptop's Settings, Display set-up.
My laptop's recommended setting (it's a Dell Inspiron 7520SE) under the heading "Change the size of text, apps, and other items" is 125%. On a whim, I selected 100%, started MuseScore 3, and the problem I had been reporting went away. Not only did the text box work on a newly opened MuseScore 3 blank score, it also worked on the score I originally submitted, which was created on a version of MuseScore 2. Moreover, the expected behavior is noted on the external monitor.
The impact on the laptop's display is that text, windows, and desktop icons reduced in size. The laptop's 125% recommended setting makes objects render 125% larger than the 100% setting.
There are only four options for this setting: 100%, 125% (recommended), 150%, and 175%.
I don't know whether there really is a bug to be addressed in MuseScore 3. I suspect so, because MuseScore 2 did not have the problem I initially reported.
Looks like we were chasing the wrong solution, kind of.
In reply to I just tried something else,… by Lawrence Iverson
//ignore this: The lesson I learned is: Use the recommended font settings on Win10 Laptops. :D
In reply to The lesson I learned is: Use… by Ziya Mete Demircan
I was using all the recommended display settings on my laptop. Up until now, I had no reason to deviate from the laptop's recommended settings. If I revert back to the recommended 125%, then I'd revert back to the originally reported text problem.
In reply to I was using all the… by Lawrence Iverson
I'm very sorry, I totally misunderstood (due to very fast reading):
The lesson I've learned has changed: Don't use the recommended font settings on Win10 Laptops, use 100% instead.