Text Edit cursor displays in wrong position

• Jan 25, 2019 - 03:30

Using Win 10 / 64-bit / Musescore v 3.0.1.5087

If I double click on text the cursor displays in the wrong position and entered / deleted text is not where the cursor is shown. This is annoying to say the least. I created a WMV file demonstrating the issue but this site does not allow that type of file to be uploaded. It is fundamentally easy to reproduce: double click on the title text of a score and start entering text. I looked to see if this had been reported before (surely it has) so regrets if this is a duplicate. Best regards.

Comments

• Jan 25, 2019 - 03:49

First of all, this is the forum and a good place to start discussions of all bugs. There is an issue tracker that programmers use to keep track of bugs that need fixed.

I cannot reproduce this bug with the same Windows and MuseScore versions. Is this all files on your systems or did you only notice it on one?

Reply

• Jan 25, 2019 - 04:49

Mike, thank you for the speedy reply.

The problem occurs on all files I've tried imported from V2, xml, and newly created. One thing I notice is that the problem occurs only when there are spaces in the text. The default font is FreeSerif. Create a new file with a title that has one or more spaces. The more spaces, the worse the problem. Might I be missing required fonts on my system? I also notice that if I select the title text at the beginning (before the first character) and enter text, then the text is in another font (Agency FB.) That seems unintended as well. Below is a series of screen shots of me double clicking text and entering new text with spaces. Hopefully that will demonstrate the problem.

This was NOT a problem on version 2. I really wish I had stayed with that version as it had no issues that I was aware of. Is there a way to reinstall V2? I no longer have the msi file for that or I would have done that already. Shot1.JPG Shot2.JPG Shot4.JPG Shot5.JPG

Attachment Size
Shot1.JPG 47.7 KB
Shot2.JPG 49.16 KB
Shot4.JPG 210.01 KB
Shot5.JPG 135.41 KB

Reply

• Jan 25, 2019 - 05:23

Just a few comments without trying to test anything. First, FreeSerif is internal to MuseScore, you would be more likely to run into problems if you have it installed as an external font. There is a known bug that if you move to the start of most text items, the font in the Text toolbar changes depending upon the system. You also get a different font of you move to the end of the text item. This is not unique to Title text. I tried a couple of things and still don't have an issue with the cursor being in the wrong spot. Hopefully someone will be able to reproduce the problem so it can be addressed. There are people better at reproducing problems than I am.

You still have version 2 on your computer unless to took action to delete it. You can still find it under your .../Program Files (x86)/MuseScore 2 folder. You can create a shortcut to it to use it if you want. Don't give up totally on MuseScore 3. It is still a work in progress and one day will be far better than version 2 could have ever been if I have anything to say about it.

Reply

• Jan 25, 2019 - 06:50

Thanks Mike;

I do not have FreeSerif installed (not listed in my MS fonts.)

I made the judgement error of uninstalling V2 and deleting the MSI. So, I have no choice it seems than to stick with V3. BTW, I have huge respect for the developers and support staff that make this program available. I'll be patient. One thing I do miss is being able to position system text anywhere I want (now its restricted to above / below staff with limits on range.) That was a big change and I imagine there are philosophical reasons for that. Would love to have a "free" text element that could be place anywhere on the score (is there one I haven't found?) I produce my lesson material with Musescore and like to mark up the scores with notes, etc.

Again, thanks for the assistance and for your time. Cheers.

Reply

• Jan 25, 2019 - 16:44

There are almost no new limits on what you can do in positioning items in version 3, just some new methods to learn. If you want to reposition a text item and other things move that you don't want to move, then remove the check from "Automatic placement" in the inspector for the item you are moving. It will then stop influencing the other items. Keep in mind, this may mean you have to disable auto placement in other items if they already occupy the destination for the text you are moving so you can adjust their position as well.

I see that drowo@gmx.net provided a link to 2.3.2 if you want to use that while version 3 is being stabilized. There are a lot of friendly people here from around the world who will help you understand if something does not work the way you expect in version 3.

Reply

• Jan 25, 2019 - 18:21

Thank you Mike; I will have to find the document on V3 changes and study it as that will likely result in a happier user experience for me. I think I just jumped into V3 expecting it to be a trivial learning curve; Automatic placement is something I overlooked; unchecking it has resolved that issue for me. Again, thanks for your time and patience with this noob.

Reply

• Jan 25, 2019 - 18:32

The Handbook link under Support in the menu at the top of this page links to the version 3 handbook, which is still very much a work in progress. This is a community effort. You may feel free to edit it if you find it lacking an explanation or use the Documentation forum to comment on it if you prefer.

Reply

• Aug 16, 2020 - 17:16

FYI. I have the same issue with my installation.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f

Notice in the screen shots above, the text frame does not align with the spacing provided for the text.
Have y'all found a root cause or resolution for this issue?

Reply

• Aug 16, 2020 - 18:35

Mrbbolt: I filed the original ticket on this and it has plagued me until just recently. I just checked the latest revision I have which seems to be the same as yours: OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f. I cannot reproduce the bug now. That makes me think the problem is external to Musescrore code, perhaps an out of date system library, graphics driver, or even a system setting that I've changed. I have installed and uninstalled various software packages over the past months and do not know exactly when the problem went away.

Maybe a Musescore software analyst can think this through- how is the display of the cursor position calculated? Is there a dependence on a system library or system setting that could be different on my current PC build and Mrbbolt's?

Mrbbolt, I hope this resolves itself for you as it did for me. I wish I could tell you HOW it resolved itself for me. That remains a mystery, it seems.

Reply

• Aug 17, 2020 - 04:47

Thanks so much for your reply.

The existing post seemed to imply that the problem was limited to your device, so I wanted developers to know that the problem is more pervasive and not limited to previous releases.

Thanks for letting me know how you resolved the issue. While the problem is associated with Musescore, your experience indicates that a work-around exists. (Hmm. Maybe it has to do with recent changes I've made to my display settings.)

I'll play around with some things.

Reply

• Aug 19, 2020 - 02:46

Hey Shelley and Marc,

Thanks for responding with the additional information.

I verified that the cursor alignment issue is associated with running in dual monitor mode with different resolutions on the two screens.

Here's my scenario.

I have a laptop and an external monitor. I've extended my Windows 10 desktop to take advantage of both displays; however I need to run the displays at two separate resolutions as per their different specs.

I run Musescore on the larger external monitor, so this is where I noticed the text cursor alignment issues.

Taking into account the reported Musescore issue associated with dual monitors, I tried dragging the Musescore workspace back into laptop's display. That corrected the cursor alignment issue.

I did not have to change any display settings, or shut down the external monitor. I just ran the Musescore workspace on the primary display.

Again, thanks for your comments. I hope these reproduction steps help the developers address the issue.

Cheers,
Brian

Reply

• Aug 19, 2020 - 19:45

I misstated the display issue.

I am not running different screen "resolutions". I am running the two monitors at different "scales". I am running the larger monitor at 100% and the smaller monitor at %125.

Scenario – Different Display Scale between the two monitors
This means that the scale percentage differs between the primary and secondary display.
Musescore honors the scale of the primary display, so Musescore misaligns the cursor and text area on the secondary monitor.

Resolve this conflict in one of three ways.
• Run the Musescore workspace only on the primary display.
• Set the two displays to the same scale value.
• Select the option in the Windows 10 display settings page to designate the Musescore monitor as the primary display.

Since Musescore sets it’s display DPI at launch any changes to the display settings require restarting the application.

Scenario – Different Display Resolutions between multiple external monitors
This does not affect the cursor or text area alignment. Only differences in scale effected the cursor and text size and alignment.

Reply

• Feb 20, 2024 - 00:11

Hello,
I do encounter the same Problem - however it looks like there is extra space behind the text - The bounding-box Calculation is buggy - see attached file: the Boxes around Text-"Übungsmarke" is Wrong the right margin is to big.
I do also encounter the "Curser-Misplacement" issue reportet by ' shelley_heard' - I couldn't describe it better.

However I state: The size of "Curser-Misplacement" meets exactly the amount of "(bounding) Box" error!!
Hint: the Curser-Misplacement is Zero at the right side of the text(box)
Hope that helps ...
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34

Attachment Size
Unbenannt.png 86.18 KB

Reply

Do you still have an unanswered question? Please log in first to post your question.