You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: