Prevent closure of the Player (unless forced) while triggers are still in the execution queue

Looks like at present, it is possible for an operator to close the Player even if an app is still right in the middle of running a trigger queue. This is leading to a potentially corrupted state of an app that, depending on what it is doing, can be close to impossible to recover from.

Please prevent this so that the Player will only close if all scheduled triggers (incl. transitions!) have been completed successfully, unless forced.

Hi @sebme -

Thanks for this suggestion! This has actually come up before from @mrios92 in his question here User closing Tulip Player mid trigger execution - and we have a couple “workaround” options, but I can understand that those aren’t ideal.

The product team will look into this further!