kicad-developers team mailing list archive

[Oliver Walters <oliver.henry.walters@xxxxxxxxx>]

Yep, understood. The new footprint wizard script doesn't actually change
the string values that are sent in from KiCad so it sends back identical
values.

On Thu, Sep 15, 2016 at 6:49 PM, Simon Wells <swel024@xxxxxxxxx> wrote:

> the problem is what happens if/when it needs to convert back into a
> string, it needs to know whether to show a comma or period
>
> On Thu, Sep 15, 2016 at 8:25 PM, Oliver Walters
> <oliver.henry.walters@xxxxxxxxx> wrote:
> > I'm not 100% that I understand the issue, but here is my proposed fix:
> >
> > Allow "native" separators in KiCad (comma or period) and when the Python
> > script converts these string values to numbers it will automatically
> turn a
> > comma into a period.
> >
> > On Thu, Sep 15, 2016 at 4:58 PM, jp charras <jp.charras@xxxxxxxxxx>
> wrote:
> >>
> >> This is a language setting.
> >> It could be no so easy to test, if the system language uses the same
> >> separator as the "C" language
> >>
> >> The easy fix is do not use the wxWidgets floating point validator (no
> >> validator).
> >> The user must enter fp numbers using the "C" locale separator (the
> point).
> >> The best fix is more complicated, and imply :
> >> - Use the selected language (usually the system language, but not
> always)
> >> fp separator to display fp
> >> number in dialog (this is not currently the case: currently this is the
> >> "C" locale separator, used
> >> by the Python script)
> >> - In countries which use an other separator (a comma), allow both the
> >> current locale separator *and*
> >> the "C" locale separator.
> >>
> >> This issue is well known in Kicad.
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>