
By Antonym
Tue Aug 07, 2007 6:07 pm
well, addressing this issue can be considered allowing for unification of operation...
OPERATION:
1 - on END param, UP zooms UP, DOWN zooms DOWN
2 - on START param, UP takes you to SAMPLE, DOWN zooms DOWN.
by its precise nature, trimming is a keystroke/data wheel/interface heavy function as it is. throwing another keystroke in there in between the user and vertical zoom when the user is working fast provides the following problems:
accident of changing viewed SAMPLE in TRIM
slowed workflow due to extra tap of button
additional wear on button
and since like i said, when trimming, esp with trimming fast, you're really using these buttons a lot to get yourself to your exact position.
OPERATION:
1 - on END param, UP zooms UP, DOWN zooms DOWN
2 - on START param, UP takes you to SAMPLE, DOWN zooms DOWN.
by its precise nature, trimming is a keystroke/data wheel/interface heavy function as it is. throwing another keystroke in there in between the user and vertical zoom when the user is working fast provides the following problems:
accident of changing viewed SAMPLE in TRIM
slowed workflow due to extra tap of button
additional wear on button
and since like i said, when trimming, esp with trimming fast, you're really using these buttons a lot to get yourself to your exact position.




