While I appreciate the immense effort that went into 0.47, I was so looking forward to some more bugs to be fixed. So I can steel myself, will it be a year or so before there is any hope of a release with another batch of bug fixes? Some examples that are important for me are 190557 and 363000 and less often hit but still important for me are 168651 and 401567. I know. Everyone thinks their bugs are the most important and I'm just whining. But I really want to believe in Inkscape and have it be a professional, reliable piece of software. When I hit these bugs every single day, it's hard to think that.

You realize that it's in version 0.47 right? Anything before version 1.0 has to be considered a beta product. If you don't expect to find bugs in beta versions then I don't know what to tell you.

llogg wrote:You realize that it's in version 0.47 right? Anything before version 1.0 has to be considered a beta product. If you don't expect to find bugs in beta versions then I don't know what to tell you.

Yes, of course. But there is a roadmap for many more 0.x versions. So that is telling me there is no intent to "finish" it. It's a volunteer project, and that is great that so many are willing to put in that work. But what is the point of all that effort if not to make an application that works to some level of quality that it will get used by a large, professional audience? In any case, it's quite arbitrary whether is is 0.47 or 1.0. There are probably many commercial product that have been released as 1.0 with as many serious bugs. But features that are clearly broken are usually fixed before long. With an open source project it is up to the whim of various developers. I wish it would go from 0.47 to 1.0 next, with just a bug fix release, but that's not my choice.

More info (not on tiled clones, but 0.47 in general).

First, some good news. Crashes are way down from 0.46! I'm not sure I saw one in pre4 even. This is a major improvement and very appreciated!

Now, the bad news. I just did a two hour job and ran into 3 significant bugs. When I have time, I'll check if any of them are reported already, but with print and pdf bugs, it's difficult for a user to know if a bug is the same as one of the ones I know are already there. The page size is "letter/landscape" if that matters.

1) I have a few grouped objects. One has subgroups, the other doesn't. Neither printed right. Group parts were just missing altogether from the print! Some of the component objects are blurred and/or transparent. I know those were big problems in 0.46, but I thought they had been fixed.

2) So backup plan for printing is to save a copy to PDF, which I want to do anyway to give to the client. No luck. Same issues as in #1 above. So I have to export the image and import that to another document. At least that works better than it did in 0.46.

3) I tried during designing to copy an object that is a group. One of the components was a 3D box (first time I've used those). When I copied the group, the 3D box was missing from the copy. I tried to make a new 3D box at that point, and couldn't get it to be visible. No fill/no stroke. Gave up and made it by hand with rectangles.

Lost more than half an hour that I couldn't bill out. Most complex (and not that complex) projects I have will not print correctly, and often not save to PDF correctly.

PS Has anyone gotten auto-save to work? I just did some more experiments, and I see no files in the directory I told it to save to.