Collision between staff text and tempo text [DELETED] 3 • Jan 3, 2018 - 14:24 Reported version 3.0 Type Functional Severity S4 - Minor Status closed Project MuseScore Tags 3.0alpha layout Regression in visual tests emmentaler-text-1 gonville-text-1 bravura-text-1 and musejazz-text-1: Collisions between StaffText and TempoText. Expected: Actual: Reply Comments Anatoly-os • Apr 2, 2018 - 08:07 Tags View Changes Reply mike320 • May 14, 2018 - 20:03 relates to #272381: [EPIC] Tempotext issues Reply handrok • Sep 6, 2018 - 13:03 Tested on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 8035689 Current state: There are no collision. But staffText is above tempoText. Is it by design? Reply handrok • Sep 7, 2018 - 12:05 Status (old) active ⇒ fixed Status active ⇒ fixed Reply System Message • Sep 22, 2018 - 10:00 Status (old) fixed ⇒ closed Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
handrok • Sep 6, 2018 - 13:03 Tested on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 8035689 Current state: There are no collision. But staffText is above tempoText. Is it by design? Reply
System Message • Sep 22, 2018 - 10:00 Status (old) fixed ⇒ closed Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
relates to #272381: [EPIC] Tempotext issues
Tested on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 8035689
Current state:
![collision.png]( "collision.png")
There are no collision. But staffText is above tempoText. Is it by design?
Automatically closed -- issue fixed for 2 weeks with no activity.