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

handle incoming messages while subject located dialog or clue dialog is open #449

Open
Tracked by #753
caver456 opened this issue Feb 13, 2021 · 4 comments
Open
Tracked by #753

Comments

@caver456
Copy link
Collaborator

maybe the right thing to do is just to keep subject located dialog and clue dialog on top. Maybe automatically set text of interrupting messages to STANDBY so that their new entry widgets don't auto-close if nothing is typed in time? Need to think more about the right way to do this.

This was observed during at least two training sessions in Feb 2021, when the subject located dialog went behind the new entry dialog when interrupting messages came in - a rare occurrence in the real world but an important occurrence for training.

@caver456
Copy link
Collaborator Author

Closed #37 from Nov 2016 - same issue - its notes:

arrange clue report and new message dialog such that new message dialog can still be seen when clue report stays on top

@caver456
Copy link
Collaborator Author

Made note of these related suggestions during testing for 3.11.5 (#742):

  • auto-standby when new entry widget is created but not raised, due to other widget continue time or child dialog/s

  • other team took focus / tab was raised when subject located dialog team lastModAge > continueTime [maybe this is OK?]

  • maybe raise child dialog when parent calls in even if another team NEW has focus and is within continue time, i.e. steal focus immediately if the incoming call has a n existing child dialog

@caver456
Copy link
Collaborator Author

If an incoming call is set to auto-standby, it would probably be good to clear the status when the NEW is raised...?

@caver456
Copy link
Collaborator Author

review #683 which is basically the same as this in title, and has several detailed fixes - did a lot of work and merged that branch to master in Oct 2023.

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