Use buttons in toolbar

[bnmajor]

This branch also needs an okay from UDRI folks since this change would affect all user workflows (although hopefully as an improvement for all).
Feedback and remaining changes:

• Make sure the frame can still be input manually
• Investigate omega to make sure that the toolbar is not being re-sized/shifting around (Note: There is no fix in this PR but I was unable to reproduce re-sizing/shifting)

[bnmajor]

@psavery There is some additional weirdness that I have noticed while testing this branch. If you click on a point on the slider the value appears to jump around rather that jumping right to that position. In this example it jumps to the last frame and the the value that was clicked on the slider:
Screencast from 03-25-2025 01:23:02 PM.webm
In this example it jumps up in increments of 10 rather than jumping right to the position:
Screencast from 03-25-2025 01:29:29 PM.webm
This does seem to happen in master as well. While I am able to confirm that additional action signals are being sent (causing this behavior) I cannot understand why or if there is a way to correct the behavior.

[psavery]

Suggested change

	def change_frame(self, value):
	def shift_frame(self, value):

Can you rename this so it's clear that we are shifting by the value, rather than changing to the value?

[psavery]

Suggested change

	self.frame.textChanged.connect(
	lambda i: self.slider.setSliderPosition(int(i)))
	self.frame.editingFinished.connect(self.on_frame_edited)

I think we should only trigger an update after the user has finished editing. Otherwise, if they type in 11, for example, it triggers an update with every keystroke (so first loads frame 1 and then loads frame 11).

But editingFinished also does not supply the new text as an argument, so you'd also have to check it with self.frame.text().

Also, we need to do some validation for the text that the user enters. I can type in invalid text like f and it produces an exception. Instead, we should do something like this:

    try:
        val = int(text)
    except ValueError:
        # Not a valid integer. Restore the previous value.
        val = prev_val

    # Clip the value to the min/max range
    val = max(min_val, val)
    val = min(max_val, val)

Notice also we should clip the value to the min/max range. If the user sets it to something outside of the range, force it to go back to be within the range.

[psavery]

We need to increase the width of the line edit based upon the max number of digits in the range. Notice that if the max value is 4 digits, when we get to the 4 digit numbers, part of the number is cut off. The below number is 1351.

For FIDDLE, it can be just wide enough to hold 1 digit, since that's all it will ever have.

Maybe you can do something like this: num_digits = len(str(max_frame_index)).