typing problem within vnl

[Cyrille]

Dear all

I am facing a typing problem within vnl.
When I want to write a number with a "point" such as 8.5 I cannot write the point.
This is quite annoying when for example I want to make a transformation (such as translation etc..) I can only use integers..

I precise that I am using vnl under windows 7 and a French keyboard (azerty).

Any idea to solve this problem?

thanks in advance

Cyrille

[Anders Blom]

Use comma.
Your locale is apparently set such that the decimal point is a comma.

[Cyrille]

I already tried that but I get the following error when using coma instead of point:

Traceback (most recent call last):
  File "C:\Program Files (x86)\QuantumWise\VNL-ATK-2016.2\Lib\site-packages\AddOns\BuilderCore\PanelPlugins\TranslatePlugin.py", line 172, in applyClicked
    translation = _computeTranslation(configuration, self.translation(), fractional)
  File "C:\Program Files (x86)\QuantumWise\VNL-ATK-2016.2\Lib\site-packages\AddOns\BuilderCore\PanelPlugins\TranslatePlugin.py", line 221, in _computeTranslation
    translation = gui_translation*Angstrom
  File ".\zipdir\NL\CommonConcepts\PhysicalQuantity.py", line 2001, in __mul__
NLValueError: Multiplying the unit Ang with "[None, 0.0, 0.0]" of type <type 'list'> failed.

[Anders Blom]

Can you please report this at support@quantumwise.com, we'll want to know a bit more details of your machine that perhaps there is no need to communicate here on the public forum. Might be a bug, that "None" looks bad. On this machine, in Excel or similar, when you want to type 4.5, do you use period or comma? In Python, what does  this print?

Code: python

import locale
print locale.getdefaultlocale()

[Anders Blom]

So, for others experiencing the same problem, it seems a workaround is to modify the Windows settings slightly.
In the Control Panel, find the "Region" settings, and click "Additional settings". 
Probably your decimal symbol is set to "," (comma) - try changing it to "." (period).
This should have no adverse effects elsewhere in Windows (except you will need to use 4.3 instead of 4.3 in Excel etc), and it seems to work around the issue in VNL.
We still intend to fix the issue, of course, so it doesn't return None when using comma if if this is the locale choice for decimal symbol.