mirdata | Python library for working with Music Information Retrieval | Dataset library

That code was written (by me) for the specific case where there is only a Next button.

It would seem that changing the first + 1 to - 1 would be the way to modify the code to create a Previous button. This sort of works, but has a couple of issues which will be explained shortly. Before getting to that, however, note that the second + 1 must remain unchanged. It is there simply to convert the zero-base stored index to a one-base index as required by the Cell property. (And yes, for the Next button only case, it would have been simpler to store the one-base index instead. Fortuitously, storing the zero-based index turns out to be the simplest method for the case of both Next and Previous buttons.)

So, what are the issues with the - 1?

Well firstly, whilst it will correctly update the index to point to the previous row of the source range, it fails to wrap from the first row of the range to the last row. Instead, it results in a 1004 error (as .Cells(sidxCurrentCell + 1).Copy evaluates to .Cells(0).Copy). This is because the assignment statement containing the Mod operator was written in the simplest way to wrap from the last row to the first row, without allowing for the reverse case.

Secondly, since the current index is stored as a static variable in the subroutine called when a button is pressed, having two such subroutines means that there are two stored indexes operating independently of each other. Thus, assuming the indexes are both set to the second row, the sequence of button presses, Next+Next+Previous, will not result in displaying the third row's value, but will instead show the first row's value.

To solve the first issue, you need to add the number of rows of the source range to the first operand of the Mod operator. (Note that with this modification the Next subroutine will also continue to work correctly.)

The second issue is solved by using a generalised Previous/Next subroutine which takes a parameter to determine the direction, and assigning two other separate subroutines to each button respectively. These helper subroutines just call the main routine with the appropriate argument value (1 for the Next button and -1 for the Previous button). Thus, there is only one stored index which is used by both buttons.

The following is the full modified code where Button1 is the Next button, and Button2 is the Previous button: