Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to edit 4th note on 4th string in a staff #419

Closed
PellTheTabber1 opened this issue Dec 29, 2022 · 1 comment
Closed

Unable to edit 4th note on 4th string in a staff #419

PellTheTabber1 opened this issue Dec 29, 2022 · 1 comment
Labels

Comments

@PellTheTabber1
Copy link

PellTheTabber1 commented Dec 29, 2022

The software acts as if the 4th string is locked and cannot be edited. I had to try to use Remove Space - even the Remove position didn't work. I would say this is a MAJOR MAJOR issue in the software. The note stays in the midi version of the piece even if shift backward is used as a desperate measure to get rid of the note. Also, selecting an entire measure and then deleting does not delete all of the notes that were selected. Another serious bug or design error. I would classify these as Design errors. In a proper design, such a bug would never happen in a million years.

Even if the entire measure is selected and Cut, the note on the 4th string at the second fret is left in the measure. What????

Additional Info
If applicable, add a screenshot or attach an example file that demonstrates the issue. In a desperate attempt to remove the phantom note, I tried to use shift backward which removes it from the screen's GUI display but the note is still there inside the midi so it plays back. This is a very serious bug, but it's now upgraded to a design issue! If removing something from the screen doesn't also remove it from the system's file version, that's a serious problem of wrong and improper design! Design flaw of a major caliber.

Version
The bug exists in all versions of Powertab on all versions of Windows for the last 10 years. It needs to be fixed before doing anything else as it's a highly critical bug. The menu items aren't enabled and disabled properly for one note in each section of the staff. Is there some sort of counter? Or are the files getting damaged?

@cameronwhite
Copy link
Member

I cannot reproduce this and would need an example file where this occurs.
One thought is that the file is using multiple voices, in which case editing operations only apply to the current voice. you can switch between the 1st and second voice in the status bar below the score

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants