search

DCS-LCSR / SignStream3

Sign language linguistics annotation software
2 stars 0 forks source link

Version 3.4.1 pre-release - In utterance window, box that appears for gloss text does not go away #611

Closed cneidle closed 9 months ago

cneidle commented 1 year ago

It happens repeatedly that the box that appears for gloss text does not go away if no gloss text is typed in.

It persists, appearing in other windows as well.

Screen Shot 2022-12-21 at 3 01 54 PM Screen Shot 2022-12-21 at 3 01 20 PM Screen Shot 2022-12-21 at 3 23 58 PM

I have also experienced some weird behavior in trying to set start and end points of text for glosses; not sure if this is related. I will see if I can replicate that.

cneidle commented 1 year ago

So, I option-click, creating that box. Then I do something else, like entering morph-phon information in another gloss. If I then use the keyboard, the text gets typed in that ghosted box, which has remained active.

Screen Shot 2022-12-21 at 3 32 42 PM

it is possible to create multiple such boxes by option clicking in more than one place.

If I hit a carriage return without entering any text, in the hope of making that box go away, I get an error message, but after I dismiss the error message, that box goes away..

Screen Shot 2022-12-21 at 3 33 22 PM

The text in the box remains if no carriage return has been entered, but it floats and does not stay with the rest of the field if the window is moved.

Screen Shot 2022-12-21 at 3 34 28 PM
cneidle commented 1 year ago

If I create the box in Utterance 3, e.g., then go to database view, the box is there. If I type in the box and hit carriage return, the text gets entered back in utterance 3.

Screen Shot 2022-12-21 at 4 18 21 PM Screen Shot 2022-12-21 at 4 18 31 PM Screen Shot 2022-12-21 at 4 18 42 PM
douglas-motto-at-rutgers commented 1 year ago

This has been observed for at least the past 3 years. While it happens occasionally, it is difficult to reliably reproduce...and therefore identify the problem. Investigating code did not expose suggestions about why this happens. May be due to old JavaSwing library implementation.

cneidle commented 1 year ago

This problem is MUCH worse in version 3.4.1 than in previous versions. It happens for me 100% of the time. And the ability to enter data into that persisting field even from the database view is definitely something I have not previously seen, although that box has occasionally remained in earlier versions. In any case, there is no problem for me in reproducing this in 3.4.1. It also persists outside of the SignStream windows, if the SignStream windows are moved.

Screen Shot 2023-01-09 at 12 34 03 PM
cneidle commented 1 year ago

This has also happened to me in 3.4.0 with text box for changing utterance name.

Screen Shot 2023-01-21 at 12 46 43 PM Screen Shot 2023-01-21 at 12 46 33 PM
gregorydimitriadis commented 1 year ago

I believe this to be due to a recent change made in #527

Moving this issue into the upcoming milestone release in order to resolve it as part of that issue.

douglas-motto-at-rutgers commented 1 year ago

It's at least not as easily reproducible now in pre_2023_02_03....although the old problem of it occasionally happening may still exist.

cneidle commented 1 year ago

see #649 and #647 and #624 and #625

cneidle commented 1 year ago

638 and #608 also related

gregorydimitriadis commented 9 months ago

Released in 3.4.1