We would like to be able to access the WWGM TK functionality from secondary threads. For example, we would like to begin our own thread from within the customization's initialize function, or from within a menu item event handler, and then return control to the user. Our thread could then perform background logic and make additional TK calls when it is necessary.
We are implementing a worker-type application where the WWGM session is basically on-call to process certain requests from a remote system. The alternative to secondary threads is to block the main thread, either from the initialize function or a UI event handler. Blocking UI event handling is not a commonly practiced approach, and blocking the initialize function keeps us from utilizing the WWGM UI in any fashion, particularly for user feedback.
We currently experience issues with this type of logic most commonly when working with workspaces, but our logical workflows general put this kind of logic early in the process.