roberto1903 / companion9x

Automatically exported from code.google.com/p/companion9x
0 stars 0 forks source link

Safety Channels wrong named in GUI 8xCH0 8xCH1; Language different to English #127

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Preconditions:
- Install companion9x Version 1.13
- Set Language to German or have a German system and set System default language
I verified the problem do not exist in English language setting, don't know if 
this is the same for other than German. Maybe other can try and report!

What steps will reproduce the problem?
1. Open companion9x and load a model setup or create a new one
2. Go to "Custom Functions" Interestingly this is not translated to "Spezial 
Funktionen" even the content of the dialog is tranlated.
3. Try to choose Safety CH3 which is not in the list of the function (second 
column) See attached picture. Instead there is 8x CH0 and 8xCH1.
4. If you select the 3rd CH0 from the list it is actually CH3 and everything 
works. Just very confusing in the GUI

What is the expected output? What do you see instead?
I would expect Safety CH1 to SafetyCH8 in the list instead of repeating CH0. Or 
translated "Sicherheit CH1" to "Sicherheit CH8".

What version of the product are you using? On what operating system?
companion9x Version 1.13; Windows7 64bit German locale

Please provide any additional information below.
This problem disappear if locale is set to English.

Original issue reported on code.google.com by open.20.fsguruh@xoxy.net on 2 Feb 2013 at 9:00

Attachments:

GoogleCodeExporter commented 8 years ago
Did you try on c9x 1.16?

Original comment by bson...@gmail.com on 10 Feb 2013 at 6:45

GoogleCodeExporter commented 8 years ago
I tried it now with 1.16; you are fast!
But no ;-( is still the same.

Original comment by open.20.fsguruh@xoxy.net on 10 Feb 2013 at 7:00

GoogleCodeExporter commented 8 years ago
Ok seen!

Original comment by bson...@gmail.com on 10 Feb 2013 at 8:00

GoogleCodeExporter commented 8 years ago
Now fixed, will be part of 1.17

Original comment by bson...@gmail.com on 10 Feb 2013 at 8:49