Hello:
I'm using the Inkscape version 0.48+devel r12685.
I'm not sure where to post this issues that i'm having with the development version of inkscape. The one that it's built for windows which download link appears in the download page of Inkscape (suv, microugly?). Here are some:

- Power Stroke: The problem appears when you apply the Power Stroke Path Effect to a closed path. When the path is closed, it seems that the path effect tries to generate a stroke of infinite thickness. Maybe I'm not expresing correctly. But It's easy to see when you create a closed path and then apply the power stroke path effect.
- Measure tool: In older development versions, that new tool was working correctly, at least It seemed to me. But In this version, with some complex paths, it has a delay, or don't appear at all, when clicking and draging the mouse. Also, this is just a wish: Could it be posible to choose to "freeze" the measure widgets that appear?. I mean, to convert the dimensions to svg entities.

- The Mesh grid "secret feature":In an earlier version(Inkscape 0.48+devel r12483) some users have managed to work with this tool, but in this vesion (0.48+devel r12685) it doesn't work good. It crashes when I try to edit the nodes.

- The New "Trace Pixel Art" tool: I import a big image, let's say a 100x100 pixel picture or bigger. I trace with the tool. Some times, or the program crash or it takes an eternity to trace the image. So, what is the limit of picture for that tool?. If the image is little, it just generates a grid of squares or a mosaic -kind of image.

So far, It's what I can see.

Any feedback is welcome

hulf2012 wrote:- Power Stroke: The problem appears when you apply the Power Stroke Path Effect to a closed path. When the path is closed, it seems that the path effect tries to generate a stroke of infinite thickness. Maybe I'm not expresing correctly. But It's easy to see when you create a closed path and then apply the power stroke path effect.

• Bug #1236320 “Power Stroke make no end lines on closed paths”

hulf2012 wrote:- Measure tool: In older development versions, that new tool was working correctly, at least It seemed to me. But In this version, with some complex paths, it has a delay, or don't appear at all, when clicking and draging the mouse.

Are you possibly measuring paths in a far more complex document, besides having installed a more recent development snapshot build?

hulf2012 wrote: (…) Also, this is just a wish: Could it be posible to choose to "freeze" the measure widgets that appear?. I mean, to convert the dimensions to svg entities.

• Bug #1222548 “Make Measure tool measurement to be persistent”
  Workaround with current implementation described here (display only, not measurement converted into objects).

hulf2012 wrote:The Mesh grid "secret feature":In an earlier version(Inkscape 0.48+devel r12483) some users have managed to work with this tool, but in this vesion (0.48+devel r12685) it doesn't work good. It crashes when I try to edit the nodes.

• Bug #1239430 “trunk: mesh gradient tool cannot assign colors to stops, crash when dragging a stop (rev >= r12532)”

hulf2012 wrote:- The New "Trace Pixel Art" tool: I import a big image, let's say a 100x100 pixel picture or bigger. I trace with the tool. Some times, or the program crash or it takes an eternity to trace the image. So, what is the limit of picture for that tool?. If the image is little, it just generates a grid of squares or a mosaic -kind of image.

I recommend to read the new tutorial included with Inkscape (see menu 'Help > Tutorials > Inkscape: Tracing Pixel Art') to learn about the purpose and intended scope of the brand-new feature (one of this year's GSoC projects btw). If you have sample (real) pixelart images which consistently result in a crash when tracing, I recommend to file a bug report, with details about snapshot build (OS, revision number), settings used for tracing, and attach the pixelart image(s).

If you are looking for more in-depth information about how libdepixelize works, you can download the developer's documentation («the algorithmic documentation report») here (PDF). The author also documented the progress of 'libdepixelze' in his blog: gsoc2013-inkscape | Vinipsmaker labs

There's also a branch by vinipsmaker (review pending), which AFAIU aims to keep the application responsive while the tracing process runs in the background.

You are aware that Inkscape's bug tracker has an 'Advanced Search' feature, right? ;-)

For your convenience - this message on the developers' mailing list has a link to a list of known recent regressions tracked for current trunk (aka what Windows development snapshot builds are based on).

Greetings
Thank ~suv for your response.
You are right, I should use better the Launchpad.
But in my defense, I would say that in some way someone have to begin to ask!; also, the problem with the power stroke, I saw that problem without aparent changes for 4 months!, so I begin to ask myself if it was just me, or what?!

@hulf2012 - it's certainly ok to ask in the user forum first whether others who also test current development snapshot builds can confirm a crash, or a regression compared to earlier builds (I often do that too, before filing a report - though using other venues than a (or 'the') user forum). My comment was a hint (based on discussions I recall from earlier topics) that IMvHO users who opt for unstable development builds can't expect to have highlights from threads on the dev mailing list (or warnings about new regressions, or notifications about newly merged features) served to them on a regular basis in a (or 'the') user forum. To stay informed about recent development at this stage isn't difficult, but might require more than downloading and unpacking the latest 7z archive… (the mailing list archives are public, the changelog is available on launchpad.net, etc.). Once the development process for 0.49 reaches the stages of alpha|beta and release candidates, this might change slightly (as announcments of such stages usually also include lists of most notable changes, and known problems).

That being said - I'm following active topics in the forum, and will (on occasion) comment as I did here.

hulf2012 wrote:I saw that problem without aparent changes for 4 months!, so I begin to ask myself if it was just me, or what?

Just a hint - your expectations about how (and how fast) Inkscape's (and other similarly structured open-source projects') development process works doesn't seem realistic to me. A time frame of 4 months isn't unexpected - on the one hand Inkscape has many known problems which are several years old (and no progress); on the other hand not all issues introduced during current development can be fixed (even if reported & triaged) immediately or just in time before branching for the next stable release.