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

LLAC improvements / ensure it doesn't cover the message field #759

Open
Tracked by #543
caver456 opened this issue Sep 10, 2024 · 1 comment
Open
Tracked by #543

LLAC improvements / ensure it doesn't cover the message field #759

caver456 opened this issue Sep 10, 2024 · 1 comment

Comments

@caver456
Copy link
Collaborator

This was during radio operator training in R6, 9/5/24. Operator had this request, and the LLAC was definitely attention-getting, but I didn't notice at the time if it was actually covering the message field.

The design is that it appears below (or otherwise not covering) the message field, and this seems to work at home. Make sure this is the case in R6.

It allows you to keep typing in the message field, but flashes and beeps on every keypress.

This points out that training is needed so folks are not too surprised by this. Maybe clean up the layout of the text in the dialog to make the two choices more obvious: 1) Ctrl-Enter; 2) Esc

@caver456
Copy link
Collaborator Author

Confirmed in r6 (3.11.5) that LLAC always appears immediately below the message field and does not obscure it. This is the case even if the NED is near the bottom of the screen, in which case LLAC is only partly visible. In that case, typing in the message field can continue, but failure to accept upon pressing enter (since enter is blocked and ctrl- or shift- enter are required to accept LLAC) would be confusing.

So, in addition to cleaning up the text layout, it would be good to detect whether LLAC has enough real estate to show below the message field, and if not, try above then right then left to find a spot with enough real estate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant