Time in Events Schedule cannot be changed back to NULL

Bug #373084 reported by Ken McLean
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenScore
Triaged
Low
Craig Mahony

Bug Description

Time in Events Schedule cannot be changed back to NULL. If I enter a Time and decide it's wrong, I cannot change it back to being blank (or NULL)

Ken McLean (kenmclean)
Changed in openscore:
assignee: nobody → Craig Mahony (cmahony)
importance: Undecided → Low
milestone: none → heatwave
Revision history for this message
Craig Mahony (cmahony) wrote :

Done and committed to Cranbourne branch.

Changed in openscore:
status: New → In Progress
Revision history for this message
Craig Mahony (cmahony) wrote :

Fix committed to main branch.

Changed in openscore:
status: In Progress → Fix Committed
Ken McLean (kenmclean)
Changed in openscore:
status: Fix Committed → Fix Released
status: Fix Released → Triaged
Revision history for this message
Ken McLean (kenmclean) wrote :

This has been fixed, but there are related bugs that make it not work.

Two related bugs are occuring:

1. When you remove time by backspace (not delete), hitting tab or enter removes the time, but takes the new time to the newly focused cell. However when you press tab/enter AGAIN, it goes back to the time that it originally was, because:
2. You cannot change a time from one value to another. It just reverts back to the old time.

Steps to replicate

1. Events > Schedule
2. Give half a dozen events a time, eg. 1,2,3,4,5,6
3. Edit the "1" time, and remove time using the backspace key.
4. Press tab or enter. The cell "2" will now have focus, but will contain the text "1"
5. Press tab or enter. The cell reverts back to "2"
6. Change the cell "3" to "9"
7. Press tab or enter. The cell reverts back to "3"

Ken McLean (kenmclean)
Changed in openscore:
milestone: heatwave → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.