Re: [Inkscape-devel] Powerstroke: adding/deleting width nodes
By now, I have forgotten all feature requests and bugs. I think all big issues are solved now, so it's ready for some proper beta testing (alert me and the maillist if you think otherwise! :P)
Yay! Looking great!
In fact, I've noticed that the Windows Inkscape development version hasn't been updated in a while: http://www.oss-marketplace.com/index.php/downloads-mainmenu-63/Inkscape/Entw... So, I haven't been able to test it on Windows. Could those folks be prodded a bit?
Right now the issues I've encountered are: - Adding a stroke to the rendered path will show extra bits of lines "inside" the stroke where at cusp corners. - Does "miter" limit only work with "miter" cusp nodes and not with "interpolate" cusp nodes? Because even when I increase that value a lot, the "pointy" edge still stubbornly remains beveled no matter what I do (more generally, I sometimes have a really hard time getting that edge to show up). - Rendering bugs sometimes.
Yes, I'll try to make some proper example files over the weekend.
Apart from that, extra features I hope for are: - Powerstroke for Ellipse shape (I know, non-trivial, but it's one of the most commonly used shapes) - More options in the toolbar drop-down corresponding to different cusp node settings (smooth nodes and either interpolate or miter nodes): "smooth" vs "sharp" lines.
I favor "pointy" lines and it's awkward to have to open the LPE dialogue each time to switch things over. It'd be even better if Inkscape could just save settings automatically and add them to the shapes drop-down, but I'm not sure if that's easy to do right now.
I've also looked at the "Apply LPE to clone" interface. It's one I can get used to, but I do admit it's a bit confusing: - It took me a while to understand what "clone original LPE" is supposed to be, and I don't think I'd have ever figured it out if it weren't for the mailing lists. How about "Clone LPE skeleton"? - How about just making this fill behavior a checkbox option for powerstroke? "Clone skeleton for fill." So, with just an extra checkbox, you can create both that complicated stroke and the fill in one go.
On 11/04/2012 15:42, Valerie wrote:
In fact, I've noticed that the Windows Inkscape development version hasn't been updated in a while: http://www.oss-marketplace.com/index.php/downloads-mainmenu-63/Inkscape/Entw... So, I haven't been able to test it on Windows. Could those folks be prodded a bit?
Click on the top-most download link (aktuellste Version), and you'll be forwarded to https://skydrive.live.com/?cid=09706D11303FA52A&id=9706D11303FA52A!128
Now scroll down the list to download the latest build from 4 days ago (r11167). Still not new enough for your tests?
hth, ~suv
On 11-4-2012 15:42, Valerie wrote:
Right now the issues I've encountered are:
- Adding a stroke to the rendered path will show extra bits of lines
"inside" the stroke where at cusp corners.
The inside of joins should look better now. Note that for extreme overlaps, it will not have improved. This is a similar issue as the following
- Does "miter" limit only work with "miter" cusp nodes and not with
"interpolate" cusp nodes? Because even when I increase that value a lot, the "pointy" edge still stubbornly remains beveled no matter what I do (more generally, I sometimes have a really hard time getting that edge to show up).
Miter limit works for both miter and extrapolated joins. The extrapolation type only extrapolates the two segments that meet at that join. They can be quite small, and then the code does not find an intersection and creates the bevel... The code should be fixed to look at longer extrapolated curves, but it will be some work.
Cheers, Johan
participants (3)
-
Johan Engelen -
Valerie -
~suv