• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 138 subscribers
  • Views 2500 views
  • Users 0 members are here
Options
Related

TD14SP1: Publication Manager how to suppress "Loading the preview could take several minutes" dialog?

Neman Syed

(Edited & condensed 2020-09-11 to reflect new knowledge & historical context this is to mitigate the behaviour of a third-party component.)

I'm opening a publication with a very large map. Every few seconds, a confirmation dialog jumps up, grabbing the focus - and keyboard - away from whatever I'm doing:

Trados Studio confirmation dialog box with a message 'Loading the preview could take several minutes. Do you wish to continue?' with options 'Yes' and 'No'.

Upon being forced to interact with it - after realizing my keystrokes are not going where I thought they were going and doing something potentially destructive - the focus stays on Publication Manager.

  1. Prevent grabbing focus. Play a sound or whatever. Just don't interrupt my work. Let me be the judge of what's important. (As an example, Outlook reminders do this perfectly.)
  2. If focus is grabbed, return focus. A few times now I've pressed the END key after acknowledging the dialog, shifting the current object from the large map down to something else. It's not possible to tell whether the preview rendering I've been getting increasingly agitated about - and prevented from completing - is continuing or aborted when my focus shifts to another object in Publication Manager. So I might be restarting rendering... I might not be restarting. Who knows?
    1. Prevent keystroke interception. It's frustrating when, say, instant messaging people, and can be really bad in general. If I'm typing a space, enter, Y, N, or a left/right arrow when it comes up, I could get completely unexpected and problematic results.
  3. When the dialog comes up, let me know what happens if I ignore it. (Discovery: It continues to render. But there's no indication either way.)

Generated Image Alt-Text
[edited by: Trados AI at 6:42 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Neman, thanks for the question. The best way to get technical attention on something like is to log a support ticket. Then the support team can match it against existing discussions, get you a useful initial reply, and route it to R&D if necessary.

    The forum is great for peer-to-peer knowledge sharing and of course us SDLers do read it as well and often reply, but the direct support route is most effective for bona fide issues like this.

    Anyway, I happened on your post and was able to get some initial info. The dialog you saw was the only way we used to be able to handle a third-party browser component we used, one that would sometimes lock the whole application if rendering took too long. (And with the whole application locked, we'd have no way to deliver further messages or intervene.)

    However, it seems that after swapping out the browser component for a more modern one that became available, this *may* no longer be an issue. We'll test this and see whether it's feasible to disable the whole dialog in an upcoming release.
Reply
  • 0

    Hi Neman, thanks for the question. The best way to get technical attention on something like is to log a support ticket. Then the support team can match it against existing discussions, get you a useful initial reply, and route it to R&D if necessary.

    The forum is great for peer-to-peer knowledge sharing and of course us SDLers do read it as well and often reply, but the direct support route is most effective for bona fide issues like this.

    Anyway, I happened on your post and was able to get some initial info. The dialog you saw was the only way we used to be able to handle a third-party browser component we used, one that would sometimes lock the whole application if rendering took too long. (And with the whole application locked, we'd have no way to deliver further messages or intervene.)

    However, it seems that after swapping out the browser component for a more modern one that became available, this *may* no longer be an issue. We'll test this and see whether it's feasible to disable the whole dialog in an upcoming release.
Children