Skip to content
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

Open
cneidle opened this issue Dec 17, 2022 · 8 comments
Open

Version 3.4 - display glitch with Translation field #610

cneidle opened this issue Dec 17, 2022 · 8 comments
Assignees
Labels
CN-Consider Consider for prioritization for fall 2023 code-complete priority MED severity MED
Milestone

Comments

@cneidle
Copy link
Collaborator

cneidle commented Dec 17, 2022

Text bunches up on the left when there are long translations.

Screen Shot 2022-12-17 at 10 54 08 AM

Screen Shot 2022-12-17 at 11 05 56 AM

@cneidle
Copy link
Collaborator Author

cneidle commented Dec 20, 2022

Same problem with December test-for-release version

Screen Shot 2022-12-20 at 11 57 18 AM

@douglas-motto-at-rutgers

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.

@douglas-motto-at-rutgers

If changes desired....need specs on that desired behavior.

@cneidle
Copy link
Collaborator Author

cneidle commented Jan 9, 2023

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.

@cneidle
Copy link
Collaborator Author

cneidle commented Mar 16, 2023

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

Screen Shot 2023-03-16 at 10 30 13 AM

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.

Screen Shot 2023-03-16 at 10 33 18 AM

Screen Shot 2023-03-16 at 10 33 25 AM

@cneidle cneidle added the CN-Consider Consider for prioritization for fall 2023 label Oct 1, 2023
@cneidle cneidle modified the milestones: Backlog, Fall-2023 Oct 3, 2023
@gregorydimitriadis
Copy link

Desired: UI would stop painting the translation field value at the end of where the utterance stops displaying.

@gregorydimitriadis
Copy link

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.

@cneidle
Copy link
Collaborator Author

cneidle commented Oct 6, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CN-Consider Consider for prioritization for fall 2023 code-complete priority MED severity MED
Projects
None yet
Development

No branches or pull requests

3 participants