It’s not easy (and a peeve of mine), but once you see the exact problem in the property editor you can develop a pretty quick workflow for the specific issues that your SVG has. Alternatively, you can also edit the SVG file to add the leading zero (or whatever is the issue).īottom line, it is a conflict in the way strings/numbers get parsed and you find a way that works for you to get it cleaned up. If you have as many as you do, I import into Ignition, close and save the view, then go into the JSON to correct the same things. Similar procedure for things not recognized as colors. Since v2. number colors right) and your error count will reduce by one. If you are able to use librsvg or the commandline version rsvg-convert for the PNG conversion. To select which one to use on your system, set wgSVGConvertervariable. This array contains a list of SVG conversion programs and the command line for each one.
An external program is required to perform this conversion. In the property editor you’ll immediately see it change from green to orange (if I remember my text vs. Therefore, it is necessary to convert SVG format images to PNG format as a fallback. Ignition re-parses the value and reads it as a number. If you only have a few you can access them in the property editor, simply select the value and hit enter. The most frequent is it doesn’t like “.7” unless there is a leading zero “0.7”. I have found the same problem, in most cases it is Ignition reading a number as text.
0 kommentar(er)
