![]() And after that, changing the width seems to work as expected.īut XML in general, and the XML Editor specifically are a little too far over my head, for me to be able to say whether the problem you see is related to the incorrect scale, or if there's something else affecting the issue. But you still have the scale problem in the file, that I mentioned to you in your other topic.įixing the scale problem changes the inline parameters. On the surface, I agree that it does look buggish. Or sometimes the problem is not where they thought it was, or well, in general, it cuts down on work by the bug managers, if we can sort of filter out some of the noise. In my experience, I'd estimate 8 out of 10 messages where people think they found a bug, turn out they just haven't learned how to do something correctly. We like to look at them first, because so many users think they have found a bug, when really they just haven't learned how to use the program. It's not because we don't trust people's searching skills to find previously reported bugs. Can anyone find this reported as a bug (or have a reason why it isn't a bug?) I searched on xml-editor in the bug databases and didn't come up with anything but perhaps that is the wrong search term. Note the inline parameters have been converted to a style correctly but the stroke-width setting has remained 0.24694389 instead of changing to the requested 10. Style fill:none stroke:#787878 stroke-width:0.24694389 stroke-linecap:round stroke-linejoin:round If you load this svg and in xml editor you select line24 and change stroke-width from 0.24694389 to 10 and press set, you will get: That script converted this svg from style to inline xml: Thus I have a python script that converts style commands to inline xml (I know Inkscape will do this if I select optimized svg, but that causes other problems in Fritzing). Fritzing (the eda package I'm using Inkscape for) doesn't fully support style. ![]() As requested in the bug reporting documentation I'm posting it here to see if I just haven't searched the bug databases correctly before reporting it. I think this is a so far unreported xml editor bug.
0 Comments
Leave a Reply. |