Hello Inkscape Community! I'm working with a team of developers that is looking to improve the Inkscape program. Specifically, we're looking for a bug that needs fixing, an issue with speed and performance, or something along that line. I've checked the launchpad bugs on Inkscape but nothing really stood out. Are there any pertinent issues that needs to be worked on?

tpatter2 wrote:Hello Inkscape Community! I'm working with a team of developers that is looking to improve the Inkscape program. Specifically, we're looking for a bug that needs fixing, an issue with speed and performance, or something along that line. I've checked the launchpad bugs on Inkscape but nothing really stood out. Are there any pertinent issues that needs to be worked on?

Welcome aboard!

I would suggest to check out the live chat and ask for/on the development channel.
https://inkscape.org/en/community/discussion/.
Also look up the development mailing list.

Pertinent issues? Depends on definition.
If you use something specific and run into the same bug all the time it can be really annoying.
Like ghosting is an issue that looks an easy task to fix, but probably regular users woud never even see it as a problem.

Then, there is the long requested user coordinate system flipping back and the ability to customize it
-which is, a tough one on compatibility with older svg documents.

How much of an issue is the ghosting problem? I wasn't able to replicate the problem on my end through the VM that I'm using.

Here's a quick renderer bug that gets frequently annoying when working with lots of blurs (but is unrelated):

1. Open inkscape, default prefs, new document
2. Draw two overlapping rects
3. Group them
4. Draw a triangular path that intersects the overlap region
5. Clip the group with the path
6. Undo

-->


This broken rendering does not go away until the object is transformed, the page is scrolled outside of the render cache zone, or the document is entirely re-rendered.

In order, in my opinion, from a user's perspective:

1 -- The bugs involving the transform attribute. For example, if you try to make a radially tiled clone, in a document which has either had it's orientation switched to Landscape, or any various transforms that might have already taken place in the file (there are many examples, if you search LP), the clones will be sprayed all over the canvas, instead of all in one place. Another issue. In the same type of document which triggers the this bug, using any extension which draws something, it could end up far outside the edges of the screen. Sometimes they are so far outside, that I can't even find them.

(There is a workaround. If you just add a new layer, and work in the layer, these problems are avoided. But imo, it would be nice to have this fixed.)

~suv is our resident bug expert, and I'm sure she can tell you which bug reports are related to this issue, if you would be interested in it. And I'm sure she can suggest what might be urgent issue from the development perspective. (She's one of very few developers who actually pariticpate here. Most of them prefer the mailing list and IRC type of forum.)

2 -- Animation!!! (https://inkscape.org/en/learn/animation/)

Welcome liam!

brynn wrote:(…) For example, if you try to make a radially tiled clone, in a document which has either had it's orientation switched to Landscape, or any various transforms that might have already taken place in the file (there are many examples, if you search LP), the clones will be sprayed all over the canvas, instead of all in one place.

We already have a fix for that (will be available in the next release), as well as for many other bugs with displaced clones (e.g. when ungrouped or moved to a different layer).

brynn wrote: Another issue. In the same type of document which triggers the this bug, using any extension which draws something, it could end up far outside the edges of the screen. Sometimes they are so far outside, that I can't even find them.

Did you test whatever specific use case / extension you have in mind with a current release? Several known bugs are already fixed - for example those with the perspective and envelope extension since 0.48.3, those with interpolate since 0.48.2, those with DXF export since 0.48.1. Without actual information I can neither look up known bug reports not tell you about the current state.

liamw wrote:Here's a quick renderer bug (…)

JFTR - tracked here (at least the variation of releasing the clip instead of undoing it):

• Bug #1428535 “Rendering incorrect when un-clipping grouped objects”

tpatter2 wrote:How much of an issue is the ghosting problem? I wasn't able to replicate the problem on my end through the VM that I'm using.

Simplest way is to set the document's background to anything but white, then zoom out to the max, and pan view outside the coloured area. If the object you zoom to is outside, the problem occours.
Even the edge at 80k shows the issue alone.


Another rendering bugs I know of are more related to cairo, like this one.

Thanks

I guess I should have been a little more clear for the kind of bugs we're looking for. We're specifically looking for data structure related bugs and issues.

Yes, when I make any changes in Document Properties all extensions run slower.
If I run extensions in default mode (all settings the same as when first down loaded) extensions are almost instantaneous.
If I make any changes they take 2 to 3 seconds to work.
I'm running windows 7, Inkscape .91, 64 bit.
I didn't have this problem in Inkscape .49.

Hello guys.
I'm glad to join your community.

1. I can confirm that I have visually the same problem as liamw on Inkscape .92, 64 bit (Win 7).

The problems persists even when I export to PNG.
I usually scroll left and right and zoom in and out a few times and it would eventually render correctly but it is really anoying.



2. I new to it and I'm not sure if it is normal but the whole program seems to run a bit laggy on my machine:

Intel(R) Core(TM) i5 CPU M460 @ 2.53GHz 2.53GHz
NVIDIA GeForce 310M with CUDA / 1GB
8GB DD3 1333 MHz RAM
SSD HDD
Windows 7 64 bit
Inkscape .92, 64 bit

When I scroll thourgh the document I get these render latency trails/artefacts:



After 0.3-0.4 seconds they are resolved when the viewport is redrawn but 1. is very persistent and does not resolve on its own.

Sorry if I'm posting where I'm not supposed to.

Known issue, I think.

Might be attributable to large file size. Here's a tutorial which gives some workarounds: https://forum.inkscapecommunity.com/ind ... article=35

That is a strange issue indeed under regular circumstances.
If you draw over the 80000 px coordinates, the ghosting issue is present on every inkscape version -known bug.
Larger portions can be missing upon different zoom levels, due to caches in the rendering process. Cache settings can be tweaked in the prefereces (Shift+Ctrl+P) though I doubt it will solve the issue as it seems a bit different.