Hi Maxime, Well, that explains why I couldn't reproduce the issue!
It sounds like the XML parser and JSON parser are expecting the comma decimal separator. Thanks for letting us know. Cory On Fri, Nov 6, 2015 at 8:09 AM, Maxime Reynaud <[email protected]> wrote: > Hi Cory, > > I have solved the problem (by chance). I have changed the langage settings > of my system from Fr to Us, and it works ! As in French we use "," instead > of "." for the decimal separator, it may have lead to misread the json > files... > > Have a good day, > > Maxime > *Envoyé:* mardi 3 novembre 2015 à 15:04 > *De:* "Cory Quammen" <[email protected]> > *À:* "Maxime Reynaud" <[email protected]>, ParaView < > [email protected]> > > *Objet:* Re: [Paraview] Colormap presets issue > Hi Maxime, > > I cannot reproduce the errors you are seeing with the file you sent. > > Do you have any problems importing the newer JSON format? You can test by > exporting a color map and then reimporting it. > > Thanks, > Cory > > On Tue, Nov 3, 2015 at 8:52 AM, Maxime Reynaud <[email protected]> > wrote: >> >> The attached file is the ColorMaps.xml corresponding to the version 4.4 >> of Paraview. I have also try to import a ColorMaps.xml from the version >> 4.1, with the same results. >> >> Thanks, >> >> Maxime >> >> *Envoyé:* mardi 3 novembre 2015 à 14:35 >> *De:* "Cory Quammen" <[email protected]> >> *À:* "Maxime Reynaud" <[email protected]> >> *Cc:* ParaView <[email protected]> >> *Objet:* Re: [Paraview] Colormap presets issue >> Hi Maxime, >> >> Can you send the .xml file that is causing you problems? >> >> Thanks, >> Cory >> >> On Tue, Nov 3, 2015 at 3:32 AM, Maxime Reynaud <[email protected]> >> wrote: >>> >>> Hi, >>> >>> I have an issue with the colormap presets. I am using Paraview >>> 4.4.0-237-g8db3c8e, and my OS is CentOS 7. The colormap xml file is not >>> correctly read by Paraview, resulting in random presets, as it is shown by >>> the attached picture. I am able to import a preset with an .xml file, and >>> to apply it. However, if I close the “choose preset” window and open it >>> again, the problem is extended to the new imported preset. Does anyone have >>> encountered this before? >>> >>> Thanks, >>> >>> RM >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc.
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
