Incomplete Vertical Line in TAB Section (Playback Mode - Continuous View) ComeBytes • Jul 23, 2019 - 22:28 Reported version 3.2 Type Graphical (UI) Frequency Once Severity S4 - Minor Reproducibility Always Status active Regression No Workaround No Project MuseScore Load the Score Choice 160% Zoom Choice Continuous View Minimize the width of the window to show only the first six measures. Playback Attachment Size Musescore 3.2.3 (Incomplete Vertical Line in TAB Section (Playback Mode - Continuous View).jpg 65.83 KB Issue - Incomplete Vertical Line in TAB Section (Playback Mode - Continuous View - 160% Zoom).mscz 11.77 KB Reply Comments Jojo-Schmitz • Jul 23, 2019 - 22:31 Step 2 is irrelevant, what matters is that the start of the system touches the left edge of the viewing area Reply Jojo-Schmitz • Jul 23, 2019 - 22:33 Frequency Many ⇒ Once Relates to #272135: [EPIC] Continuous view issues Reply ComeBytes • Jul 24, 2019 - 11:21 In reply to Step 2 is irrelevant, what… by Jojo-Schmitz Certainly. I thought Step 2 was better to see the Problem. Reply ComeBytes • Dec 5, 2019 - 12:51 In reply to Certainly. I thought it was… by ComeBytes It is very hard to see all the new versions of this Great Software with the same simple error, even more, knowing that Version 2 did not have it. Reply Jojo-Schmitz • Dec 5, 2019 - 12:53 It is waiting for someone sufficiently interested and knowlegable to fix it. That someone could be you, it is Open Source ;-) Reply ComeBytes • Aug 8, 2020 - 17:30 There is a New Version and it has this same bug. Reply Jojo-Schmitz • Aug 8, 2020 - 17:49 That is why it isn't marked as being fixed ;-) Reply ComeBytes • Aug 12, 2020 - 10:15 In reply to That is why it isn't marked… by Jojo-Schmitz Are you sure? If you do not tell me, I do not consider. I think it's so Funny. Thanks a Lot. ;-) Reply ComeBytes • Aug 12, 2020 - 10:16 In reply to That is why it isn't marked… by Jojo-Schmitz ;-) Reply Jojo-Schmitz • Aug 12, 2020 - 10:28 Sometimes bugs get fixed by accident though (and then of course without being marked as fixed here) ;-) Reply
Jojo-Schmitz • Jul 23, 2019 - 22:31 Step 2 is irrelevant, what matters is that the start of the system touches the left edge of the viewing area Reply
Jojo-Schmitz • Jul 23, 2019 - 22:33 Frequency Many ⇒ Once Relates to #272135: [EPIC] Continuous view issues Reply
ComeBytes • Jul 24, 2019 - 11:21 In reply to Step 2 is irrelevant, what… by Jojo-Schmitz Certainly. I thought Step 2 was better to see the Problem. Reply
ComeBytes • Dec 5, 2019 - 12:51 In reply to Certainly. I thought it was… by ComeBytes It is very hard to see all the new versions of this Great Software with the same simple error, even more, knowing that Version 2 did not have it. Reply
Jojo-Schmitz • Dec 5, 2019 - 12:53 It is waiting for someone sufficiently interested and knowlegable to fix it. That someone could be you, it is Open Source ;-) Reply
ComeBytes • Aug 12, 2020 - 10:15 In reply to That is why it isn't marked… by Jojo-Schmitz Are you sure? If you do not tell me, I do not consider. I think it's so Funny. Thanks a Lot. ;-) Reply
Jojo-Schmitz • Aug 12, 2020 - 10:28 Sometimes bugs get fixed by accident though (and then of course without being marked as fixed here) ;-) Reply
Comments
Step 2 is irrelevant, what matters is that the start of the system touches the left edge of the viewing area
Relates to #272135: [EPIC] Continuous view issues
In reply to Step 2 is irrelevant, what… by Jojo-Schmitz
Certainly. I thought Step 2 was better to see the Problem.
In reply to Certainly. I thought it was… by ComeBytes
It is very hard to see all the new versions of this Great Software with the same simple error, even more, knowing that Version 2 did not have it.
It is waiting for someone sufficiently interested and knowlegable to fix it. That someone could be you, it is Open Source ;-)
There is a New Version and it has this same bug.
That is why it isn't marked as being fixed ;-)
In reply to That is why it isn't marked… by Jojo-Schmitz
Are you sure? If you do not tell me, I do not consider. I think it's so Funny. Thanks a Lot. ;-)
In reply to That is why it isn't marked… by Jojo-Schmitz
;-)
Sometimes bugs get fixed by accident though (and then of course without being marked as fixed here) ;-)