February - Bug Accelerator 2023
March 1, 2023, 3:51 a.m.
Welcome to this blog entry about the Bug Accelerator 2023 program. We hope to document the work that we have done for the Inkscape project in these blog entries, please subscribe to the rss feed if you would like to see the future entries. For a breakdown of the issues which are being fixed for the release, please see this gitlab page.
We start off February as the first month of the project mid way through, with only a week and half left in the month so this is going to be a short update:
Martin Owens
- Fixing the marker issues started with report #3363 but ended up with a much more substantial refactoring. Centralising the code which decides the orientation of the marker and it's context colors. There is more work that could be done to improve markers, but this refactoring fixes lots of issues in various parts of inkscape which need to render markers to various outputs such as #3964 and #1973. !5092
- A related issue in #3744 with markers which turned out to be a problem in Firefox and not fixable in Inkscape.
- An issue with the paste in place feature in #3527 required deciding when an element should be pasted on top of or inside of, if the selected element was a layer. !5102
- An issue with rendering fonts on windows, using pango and font-manger in #4071 is still undecided. Though a fix was made to limit Inkscape to certain versions of pango in an effort to fix it.
- an issue in the how the xml parser worked specially for the namedview element caused a series of problems in #4092 and #4052 which were all fixed in !5100 the specific issue with desk colors was also given attention, so these colors were not guessed at run time, but defined by the selected theme.
- A crash in a bad svg which contained a near zero sized arc in #4110 was fixed by catching the thrown errors and dealing with the rendering issues. !5097
- A crash when closing the export dialog in #4120 was fixed by keeping the previews clean and not refreshing once closing. !5118
- An old text bug involving Inkscape 0.92 and lower produced files in #2754 blank lines would disappear or appear in the wrong places. Fortunately the fix was a combination of undoing a previous fix and applying a more subtle css style based inhereince rule to account for the previous version's bad rendering. !5119
- Finally we had some resource problems in #4122 with the export dialog. If it was open, large files with many pages would take a long time to render. Fixing this required unpicking some of the over-zealous preview updating as well as putting the rendering into an idle process so the rest of the GUI could at least load. More work is needed to make Inkscape's drawing processes thread safe to really fix this issue properly though. !5122
- Various merge requests and issues were tested, and reviewed in order to help move fixes from other developers in.
A total of 33 hours were used to complete this work over two weeks.
Rafael
Rafael has not started yet and will be starting in March.