-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3.4 - display glitch with Translation field #610
Comments
On 3.4.1_pre...it appears text starts on the left and continues as long as needed to print the entire text. This may overflow the text past the right end of the utterance, depending if the text displayed is longer than the utterance displayed. EX:...a zoomed out slider will cause a short utterance length, but the text length remains the same no matter the zoom level selected. I appears this is also happening in the examples above. |
If changes desired....need specs on that desired behavior. |
Nothing should be displayed in the translation field for one utterance (e.g. U2) from the translation field of a previous utterance (e.g. U1). So, the translation field for U1 will only display as much of that translation as fits within the space prior to the next utterance. (It's Ok if it spills over into empty space between utterances.) In order to view the whole translation for U1, the user will either need to click on the field so that it is editable, in which case the user can scroll further to the right; or else change the Zoom so that the whole translation fits in the space for the Utterance. Thanks. |
This problem is exacerbated by the fact that the translation does not always show up as left-aligned with the utterance... This from RIT-P02-s01.ssc, for example - using current release 3.4.0 on Big Sur Clicking on the translation field in U1 shows a very long region of blank space that does not seem to be deletable. Below are two screenshots resulting from clicking in the translation field at the frame shown by the green alignment indicator. |
Desired: UI would stop painting the translation field value at the end of where the utterance stops displaying. |
Carol - what if we we stop displaying the text at the end of the utterance, regardless of whether there is text immediately following it or not? It might be easier to account this way. FYI, it is unclear exactly how we would tell exactly where to cut off the text. Will have to look into it to see if it's possible. |
Sure - the display of the translation should not extend beyond the
end of the utterance, regardless of what comes afterwards.
The user can scroll through the translation field to see the
remainder of the information not initially displayed.
Thanks!
… On Oct 5, 2023, at 3:48 PM, Greg Dimitriadis ***@***.***> wrote:
Carol - what if we we stop displaying the text at the end of the utterance, regardless of whether there is text immediately following it or not? It might be easier to account this way.
FYI, it is unclear exactly how we would tell exactly where to cut off the text. Will have to look into it to see if it's possible.
—
Reply to this email directly, view it on GitHub <#610 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADH7NQTAPD7NCMNEM4XJOTLX54FKVAVCNFSM6AAAAAATCARQPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGU2DMMJTGY>.
You are receiving this because you authored the thread.
|
Text bunches up on the left when there are long translations.
The text was updated successfully, but these errors were encountered: