If a translation fails, the error can be quite hard to find from a huge log file in Translation Log window. I'm using Find Text button for that, but it would be faster to have a button, which would take you straight to the first error in the log. When clicking it again, it would go to the next error in the log.
Released
Go to error button to Translation Log window
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+5- Supporter
This is a great idea (because I also had it, so it must be), and would be very useful.
An alternative design might be several toggles beneath the current four buttons (word wrap, find, find next, settings) that allow us to show/hide the various message classes (STATS, INFORM, WARN, ERROR), so we can pick and choose which ones to see.
+22- Safer
Hi @geolassi, I'm pleased to let you know that in our latest 2018.0 betas you have the option to filter the translation log based on errors, warnings, or informs. If you were to turn on the error filter, you can use the side arrows to skip back and forth between error messages.