X-axis in >Text Style>"Rehearsal letters" shows as a negative number, but no change in position. xavierjazz • Nov 1, 2010 - 21:18 Type Functional Severity S4 - Minor Status closed Project MuseScore r3507 XP SP3 As in the title. Tnaks again to everyone. Regards, Reply Comments xavierjazz • Nov 1, 2010 - 21:35 Sorry, more info. When opened, the x-axis shows as "0". When it is changed to a negative number, the 1st post explains what happens. Regards, Reply David Bolton • Nov 1, 2010 - 23:12 Status (old) active ⇒ needs info Works for me using 0.9.6.3 stable (r. 3507), Windows 7. Please review the guidelines for writing bug reports Reply chen lung • Jul 4, 2012 - 02:47 Are you able to reproduce in the latest nightly builds? Reply ChurchOrganist • Jul 4, 2012 - 13:24 I can't reproduce in Rd697e22/Windows XP Pro Sp3 So maybe it's been fixed Reply [DELETED] 5 • Jul 4, 2012 - 14:42 Status (old) needs info ⇒ fixed Reply System Message • Jul 18, 2012 - 14:45 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
xavierjazz • Nov 1, 2010 - 21:35 Sorry, more info. When opened, the x-axis shows as "0". When it is changed to a negative number, the 1st post explains what happens. Regards, Reply
David Bolton • Nov 1, 2010 - 23:12 Status (old) active ⇒ needs info Works for me using 0.9.6.3 stable (r. 3507), Windows 7. Please review the guidelines for writing bug reports Reply
ChurchOrganist • Jul 4, 2012 - 13:24 I can't reproduce in Rd697e22/Windows XP Pro Sp3 So maybe it's been fixed Reply
System Message • Jul 18, 2012 - 14:45 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
Sorry, more info.
When opened, the x-axis shows as "0".
When it is changed to a negative number, the 1st post explains what happens.
Regards,
Works for me using 0.9.6.3 stable (r. 3507), Windows 7.
Please review the guidelines for writing bug reports
Are you able to reproduce in the latest nightly builds?
I can't reproduce in Rd697e22/Windows XP Pro Sp3
So maybe it's been fixed
Automatically closed -- issue fixed for 2 weeks with no activity.