Right now, if there are multiple tactile renderings created (e.g., the textbook diagram handler, and the photo tactile handler), and the user clicks "Send to Monarch", only one of the renderings is sent to the Monarch. Since we don't currently have access to keysoft, we have not implemented a selector on the Monarch to choose between multiple renderings. For enabling this scenario after we have access to Keysoft, the plan is:
When user turns on Monarch in options panel, they get the dropdown with "Send to Monarch/TAT" options enabled in the browser
Choosing Send to Monarch requests only Monarch experiences, and they are sent to the Monarch, where user can choose between them
Choosing Send to TAT requests only Monarch experiences, and brings up the renderings list, so user can choose which to send to TAT (is this option really useful then?)
Note: maps behaves the same way. QUESTION: Should charts work the same way as well? I assume yes, this applies to all graphic types...
Note this is similar to the earlier behaviour that we temporarily removed in #427
Right now, if there are multiple tactile renderings created (e.g., the textbook diagram handler, and the photo tactile handler), and the user clicks "Send to Monarch", only one of the renderings is sent to the Monarch. Since we don't currently have access to keysoft, we have not implemented a selector on the Monarch to choose between multiple renderings. For enabling this scenario after we have access to Keysoft, the plan is:
When user turns on Monarch in options panel, they get the dropdown with "Send to Monarch/TAT" options enabled in the browser
Choosing Send to Monarch requests only Monarch experiences, and they are sent to the Monarch, where user can choose between them
Choosing Send to TAT requests only Monarch experiences, and brings up the renderings list, so user can choose which to send to TAT (is this option really useful then?)
Note: maps behaves the same way. QUESTION: Should charts work the same way as well? I assume yes, this applies to all graphic types...
Note this is similar to the earlier behaviour that we temporarily removed in #427