Set thread culture to English so DB Author can debug properly any reported exception.

[Unknown Player]

Using DemonBuddy it throws an exception on my current language (Spanish):

System.InvalidOperationException: El subproceso que realiza la llamada no puede obtener acceso a este objeto porque el propietario es otro subproceso.
en System.Windows.Threading.Dispatcher.VerifyAccess()
en System.Windows.Threading.DispatcherObject.VerifyAccess()
en System.Windows.Media.Visual.VerifyAPIReadWrite()
en System.Windows.Media.VisualCollection.Clear()
en (VisualCollection )
en Demonbuddy.TerrainVisualHost.‬‪*‪‫‫*‏*‫‏‫**‬‪‏​‏​**‬*******()
en Demonbuddy.TerrainVisualHost.‫***‏‬‏*‫‏‏​*​‏*‬‪*‏*​**(Object , EventArgs )
en Zeta.Bot.GameEvents.‎‬​‪‎**‪​*​*‏​‪**‪​‎‫‬​*‎‬**[
](EventHandler`1 , Object ,
)

I'm not reporting the exception problem, I'm here reporting the behavior that DemonBuddy has to show an exception, because as you can see the exception message is in my current language, what if I should send you a log? you will not understand the exception message, and since English lang is the most used language, then I suggest you to set the threads culture to English ("en-US") so exception messages will be shown and will be reported to you in English.

This can be considered as a design issue or not depending on the circunstances, I consider it as a design issue because is not the end-user who is supposed to debug the exceptions that are shown by DemonBuddy, and it is easy to solve as I explained, just specifying the application culture (this means, the main UI thread culture, and the other threads culture) using the proper CultureInfo object.

Thanks for read!.