I am running Linux 22.04 LTS, and Shotcut ver 25.11.2 installed by SNAP.
Try the following experiment:
Click on a video clip on the timeline.
Select the Properties window.
The Speed field will be populated with the current speed (default: 1.0000000
Use your cursor to select 1.0
Type in 1.1
The leading 1 will be ignored, and the speed field will display .100000
The first character you type is ALWAYS ignored of you have selected more than one character in the field. This is not the case in many of the other input fields (e.g. the Size fields in the Size, Position and Rotate filter.
This will not be addressed. You need to either select all of the numbers or delete more of them. It does not accept the first digit you typed because it only accepts a maximum value. By replacing the “1.0” with “1”, which is what is happening, you are actually creating the value “1000000”, which is far greater than the maximum value for this field.
Ok, at least I see the logic; but I would argue that since there is a separate Apply button, any intermediate values created in the text edit field should be ignored - the time for error checking is when the Apply button is clicked.
(This problem could be avoided altogether by reducing the number of significant digits in the input field.)
Thanks for your response - I’ll just be more careful in the future!
This is a Qt numeric field with a maximum value. The reason for large amount of decimal digits is for high precision because some people are using for conversion between weird frame rates; NTSC rates is particularly unfriendly as is also fraction. The UI library’s numeric field does not have separate minimum & maximum decimal digits, only a fixed amount. I am not going to change this to a text field and add a bunch of logic to teach it about numerics.
Do you think it will help to automatically select all when the field gets focus?
Probably not - I can see times where someone might want to tweak a value just a little bit. Given your constraints, I think you are in the best possible place.