Hey

There is a general problem I've been having with Inkscape. I haven't been able to solve it in a satisfying way (I have searched the forum and the list of bugs), so I found a "hack" to come around it. If you create two objects of same colour with a common edge, you will see a line where the two edges meet caused by the way AA works. It's the same problem that is described in this blog http://petewarden.typepad.com/searchbrowser/2011/01/a-fundamental-bug-in.html"smilies" src="images/smilies/icon_e_sad.gif" alt=":(" title="Sad" />


Mark

Hi Mark,
Yes, a frustrating bug. I suspect that ~suv will chime in with any relevant particlars, bug-wise. But meanwhile, as for workarounds, it probably depends on your unique drawing and what's happening there. Slighly ovelapping the objects is one way to go. Another might be to place a bigger object of the same color below the joints in z-order. In some cases, one might choose to keep strokes in place, which would cover up the "gap". Or maybe a filter could be made that would have the effect of stitchng them together, or even an extension maybe could be written??

I'm afraid that's about all I can come up with

Bug #170356 in Inkscape: “Suppress antialiasing artefact at the object boundary”

Read the comments 1, 3 and 5 in duplicate Bug #166252 “Cannot align boxes properly.” for further details - from a developer's POV.

Thanks for the replies . I guess I will just use the method I've been using so far. It works fine, I just don't think it should be necessary and it's kind of annoying when I show Inkscape to other possible users. I have subscribed the bug to know when there is progress. I just wish it would get a higher priority.

Edit: I read the comments in the duplicate bug. It says that other vector applications has the same problem, but I don't see it in Flash. Why is that? Someone said that Flash rasterizes at 4 times the desired size, and then scales it down afterwards. Do any of you know if this is true? (Is it the same method games use?)

Here is a very simple filter which does the job. Unfortunately it doesn't work well on object with transparency because it works on Alpha channel.

Select your object, open the Filters Editor and check the box left of the filter name.

The only entry changed is set to 1.8. That's the minimum for horizontal and vertical straight lines while 1.5 is enough for other lines.

ivan

You can use a workaround in some cases:

http://wiki.inkscape.org/wiki/index.php ... ll_visible.

http://wiki.inkscape.org/wiki/index.php ... liasing.3F

I tried different workarounds to apply transparency to shapes filtered with the "Stitch" filter above and the best one is grouping and applying transparency to the group.

ivan

Thanks again for the replies I will just use the workarounds then. My biggest issue with this was that I thought no one else had had these problems (or didn't care), but it seems that I just didn't use the right keywords when searching.

it's not so bad though. there's plenty of other display related issues that are to do with inherent hardware/OS issues, and there's no-one to talk to about those. i find consumer LCD screens particularly bad. Windows OS keeps changing about font smoothing in different versions of windows, etc.
just so you don't feel so sad....bare in mind that all svg objects have an inherent (display) order, which is part of the design (of the specs).
and as my daughter used to say ARGHHHHHHH, THERE's A BEAR IN YOUR MIND.

I have subscribed the bug to know when there is progress. I just wish it would get a higher priority.

While we are blessed that Inkscape is open source, thereby allowing ordinary users to request new features, report bugs, etc, bugs and new features are not neccisarily addressed by developers according to user requests/popularity. I've reported bugs which went inactive for a year, before someone apparently took notice. So even though it does not have a high priority now, doesn't mean that it won't change in the future. The developers keep somewhat of a priority list/roadmap, that is constantly discussed and adjusted (as I understand the process). With this particular bug, which has several comments spanning several years, including several duplicate bug reports -- I'm sure it has attracted attention!

Although this brings up a question for me, which I hope ~suv or others can address. Which is more powerful support for a bug or new feature request, as far as attracting developer's attention and getting fixed or added -- a comment added to the bug report, or subscribing to the report ("Does this bug affect you?")? Or are they relatively the same?

brynn wrote:

I have subscribed the bug to know when there is progress. I just wish it would get a higher priority.

While we are blessed that Inkscape is open source, thereby allowing ordinary users to request new features, report bugs, etc, bugs and new features are not neccisarily addressed by developers according to user requests/popularity. I've reported bugs which went inactive for a year, before someone apparently took notice. So even though it does not have a high priority now, doesn't mean that it won't change in the future. The developers keep somewhat of a priority list/roadmap, that is constantly discussed and adjusted (as I understand the process). With this particular bug, which has several comments spanning several years, including several duplicate bug reports -- I'm sure it has attracted attention!

Although this brings up a question for me, which I hope ~suv or others can address. Which is more powerful support for a bug or new feature request, as far as attracting developer's attention and getting fixed or added -- a comment added to the bug report, or subscribing to the report ("Does this bug affect you?")? Or are they relatively the same?

The bugs are all triaged fairly quickly - please remember however that there are many bugs that involve crashing or causing instability. These will always take higher precedence over feature enhancements/requests or quirky behaviour.

-Rob A>

brynn wrote:Which is more powerful support for a bug or new feature request, as far as attracting developer's attention and getting fixed or added -- a comment added to the bug report, or subscribing to the report ("Does this bug affect you?")? Or are they relatively the same?

Please use "Does this bug affect you?" (and optionally subscribe to the report). Refrain from commenting unless you have a new and previously not mentioned observation or insight to add about the issue.

Honestly, any "Me too" or "1+" comments are (at least IMHO) just annoying and do not help the cause of getting the bug fixed or the issue addressed (a bug tracker is not a forum).