kicad-developers team mailing list archive
Mailing list archive
Re: Should I start a new bug or is the reopened one suitable?
Thanks - next time I'll open a new report and ref the old one. But I won't bother for this one, since Wayne has already commented about it on gitlab.
On 5/27/22 01:53 PM, Seth Hillbrand wrote:
You commented in that bug report with the details. Usually, commenting in open reports with examples that show the issue is sufficient.
If the issue were already closed, then opening a new report and referencing the old one is preferred.
On Fri, May 27, 2022 at 10:48 AM Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>> wrote:
I recently reopened an issue  because I found an old schematic that could be opened properly by 5.1, but which gave "missing symbol" boxes when opened with 6.0 and 6.99.
However, while the effect is the same, the root cause may be different, so maybe reopening the bug was the wrong approach. Should I instead start a new bug for this?
Looking at the .sch files, the original has entries like:
L RES-10M-5%-1/4W-CF R5
But after opening and saving the schematic with 5.1, this component has changed to:
L e202var-vlf-radio-receiver-rescue:RES-10M-5%-1_4W-CF R5
At that point, 6.0 and 6.99 can correctly open the newly saved schematic.
Thus, it looks like 6.0 and 6.99 have lost the ability to deal with a "/" in a component name. I don't know if any other special characters also fall into this category.
 https://gitlab.com/kicad/code/kicad/-/issues/11563 <https://gitlab.com/kicad/code/kicad/-/issues/11563>
Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
KiCad Services Corporation Logo
Long Beach, CA
www.kipro-pcb.com <https://www.kipro-pcb.com/> info@xxxxxxxxxxxxx <mailto:info@xxxxxxxxxxxxx>