In Studio 2017 some error messages may be well overkill. They should simply get to the point right then and there.

Former Member
Former Member

This new feature of Studio 2017 of allowing the user the find "Knowledge Base" and "Community" links to specific errors is a good idea, BUT not always. Case in point, you open a translation project whose TM(s) or Termbase(s) no longer exist or their names have been changed and whatnot and all the user expects to see is two things. 1) First, a message, a warning message (usually with a yellow icon) and not a "critical" error message (the red icon with the letter X); 2) the name of the culprit: TM, Termbase, etc. The rest is overkill. Saying "Unable to find the specified file" does not help me at all: Which file?!  Dear developers, please take note of this. Thanks.

Parents Reply Children
No Data