Timecode editing zeros out lesser values

[powlow]

Wondering about the logic behind lower values of Timecode being set to zero when editing a specific part of timecode in the transport.

So for example, editing minutes will set seconds and frames to 0.

Clicking on minutes and then using up and down arrows does not zero out the lower values.

Just wondering what the logic behind this is and how this is useful to people.

Any real world examples would be great and much appreciated!

[nednednerb]

Just that, the difference in outcome you suggest.

However, I experience the function differently.

When I type "3" and hit enter, I can expect 3.0:0 to get selected, etc.
When I select the "3" and just cycle that digit, I can expect just that digit to change.

Therefore, remembering the difference, I can choose to set the timecode exactly or get a "whole number" or just vary the min or sec and keep the other place value intact.

I think the above makes more sense, rather than if turning the selected 3 the lower value would change, and opposite with entering 3 and hitting return to keep the value.

Sent from my Pixel 6 Pro using Tapatalk