UI bugs related to rests

  • In any key where the tonic is A or A with accidentals, it is impossible to change notes into rests by pressing the “rest” button or entering 0. (Chords are okay.) The same goes for notes within modulations using those keys.
  • When a note or chord is turned into a rest, Hookpad still previews that note or chord as if it were moved to scale degree 7.
  • When inputting rest notes, they follow the previous note’s octave and respond to Up / Down, even , and .. (Existing rest notes cannot be transposed.) This is an annoyance more than a bug; all rests reset to Middle C after switching the entry mode back and forth.
  • When a rest chord is inserted before any non-rest chord, and the cursor is positioned after the rest but before the first non-rest chord, the note palette indicates with the blue dots that notes on the tonic chord are stable. This happens on both entry modes, but is more common on text mode due to rest chords being mandatory.
    image

@HertzDevil, thank you for the update today on this. We are working on fixing these.

As always, thank you so much for the amazing bug reports :clap:

Fixed in 2.11.10

Fixed in 2.11.10

Will address other two issues in upcoming build.

EDIT

Fixed in 2.12.0

Fixed in 2.12.0

Turning a note into a rest doesn’t reset its “octave”, but otherwise these issues seem fixed.

Also add one more: relative key changes also move the “scale degrees” of the rest notes.