- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Powerstroke: adding/deleting width nodes
by Valerie 21 Apr '12

21 Apr '12

Strange, I seem to be having rendering problems now. See first attached file: sometimes (once every few renders) the render doesn't update after moving nodes or the width control. It takes moving things around a bit more before it renders again. I'm not sure if it's a Powerstroke problem or some other render problem, though I don't seem to have the same issue with normal paths or Pattern along Paths. The inside of strokes looks great for the most part now! It still renders "inside" for sharp angles. Also, it seems hard to make very sharp Extrapolated edges again. See second attachment. I've increased the miter limit to 400, and the edge does render under Miter mode, but not under Extrapolated mode. You're right about the UI, some discussion is needed. And then it needs to be coded (I can't code, unfortunately). It's a pity, because this is a feature that's bound to be very popular, and UI issues would slow down the workflow. Message: 6 Date: Fri, 20 Apr 2012 21:41:17 +0200 From: Johan Engelen <jbc.engelen@...2592...> Subject: Re: [Inkscape-devel] Powerstroke: adding/deleting width nodes To: inkscape-devel(a)lists.sourceforge.net Message-ID: <4F91BBDD.4080701@...2592...> Content-Type: text/plain; charset="iso-8859-1" On 16-4-2012 4:03, Valerie wrote: > > The inside of joins should look better now. > > Thanks! And actually, I think I found the reason for my "hard to > make points appear" issue. And I think it might have been > resolved since. See the attachment. > > I made that example in a version of Inkscape on Windows. As > you can see, if the control point was on one side, the pointy edges > would not appear. But moving them to the other side somehow > fixed the problem. So it had nothing to do with miter limit! > Yep you found the reason, and yep I had it already fixed :) > Apart from that there's some rendering issues for large lines, > but those are extreme cases. It's definitely quite nice to use > now! > Struggling with thick lines too... but I think it will be hard to fix as I think the 'bug' is actually 'correct' mathematical behavior. > Now my main wish-item involves quickly accessing settings. > The most accessible way may be to have a drop-down option > for "Last powerstroke settings" (shorter name needed...) > Being able to save each settings and access them from the > toolbar drop-downs would be even better, but that doesn't seem > to be trivial to do right now. All ideas are welcome. Help would be nice: UI stuff is generally not particularly difficult to code, but time consuming (and of course you need to decide what you want). I recently did quite a big "mathematical" change, so perhaps new bugs popped up... but it was supposed to fix the "instable" rendering stuff (where you see flickering joins for example). Cheers, Johan

1 0

Parallel build on Windows
by Johan Engelen 18 Apr '12

18 Apr '12

Hi all, For parallel builds on Windows, update to >= rev11088, recompile buildtool: "g++ buildtool.cpp -o btool.exe -fopenmp" and run "btool -j" (or "btool -j x", x=number of threads to use) I fixed the bug, and with virusscanner disabled, I can build Inkscape clean in 5 mins and 2 seconds. (i7 2600) Cheers, Johan

2 1

Re: [Inkscape-devel] Snapping
by gespertino＠...400... 17 Apr '12

17 Apr '12

2012/4/17 Vladimir Savic <vladimir.firefly.savic@...400...>: > Why not even setting it to zero? I do it almost immediately upon new > install. Although, I admit that even having an option for delay is great, > especially as drawing gets more complex. > > If you choose to change it (but not zero it) - half way down from default > will work, I guess. There was something witn zero delay, I can't remember what (and it probably was fixed already). I think it was something related with performance, but I'm not sure. I should check my bug reports and see what was the problem (and if it still exists), but I remember having to use a small delay to avoid it. Anyway, If snapping with zero delay doesn't conflict with other tools or something, I can agree that it's a much pleasing default, so +1. Gez

3 2

Re: [Inkscape-devel] Powerstroke: adding/deleting width nodes
by Valerie 15 Apr '12

15 Apr '12

> 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/Ent… 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.

3 2

Example for Inkscape extension in Java?
by Gerrit Karius 15 Apr '12

15 Apr '12

Dear Inkscape devs, Can anyone point me to a working example of an Inkscape effect extension written in Java, running on Windows? I've read the Script_extensions and INX_extension_descriptor_format wiki pages. I thought, theoretically I might just replace the command tag in the inx file with something like this: <command reldir="extensions" interpreter="java">Hello</command> And then I could call a Hello World program like this one: class Hello { public static void main(String[] args) { for( String arg : args) System.err.println("Hello error: "+arg); }} The program wouldn't return any document, but the error message would be displayed by Inkscape. However, when I test this, nothing gets displayed. When I change the program to write a file, that file doesn't appear either, so I guess the program isn't called. I can change the command text to any other value, but there is no notification that a script couldn't be found. I have written several Python extensions, but those hook up into the existing Inkscape Python extension framework, with inkex.py and everything. Maybe there's some hidden magic in there that I missed? Can someone point me to a working Java example, or tell me what I did wrong here? Many thanks in advance!Gerrit

2 2

GTK+ 3 build option
by Alex Valavanis 14 Apr '12

14 Apr '12

Hi All, I've added a new configuration option in r11244 to allow building against GTK+ 3. configure --enable-gtk3-experimental Note that this is only useful for people who want to get involved with the migration project... at present, all builds with this option enabled will fail! The option also automatically searches for a compatible external GDL library (>= 3.3.4), and uses that instead of our fork. Cheers, AV

1 0

Inkscape Translations
by Josh Andler 12 Apr '12

12 Apr '12

Hey All, It's been quite a while since we've called on the translators to do your magic. There have been over 800 string changes (last number mentioned to me) since 0.48. This is in no way announcing a string freeze or anything along those lines. It's purely just a friendly reminder that you can probably safely do your greatly appreciated work at this point and you will probably be 90-95% done come the actual string freeze. No release plan at the moment, but as soon as we have one, you will obviously be notified. Cheers, Josh

2 1

Inkscape 0.49 Release Notes up to date?
by Josh Andler 11 Apr '12

11 Apr '12

Hey All, I think the release notes probably need to be looked over by everyone who has contributed significant code during this dev cycle. http://wiki.inkscape.org/wiki/index.php/Release_notes/0.49 I don't see mention of the "remembering" opened dialogs between sessions or the improvements to the gradient tool controls bar for example. This is just a call to make sure things are documented, not in any way reflective of an impending release (although I will request people take another look again prior to the next major release). Also, do we really not have more notable bug fixes in this release that weren't backported? Cheers, Josh

1 0

Drawing speedup
by Jon Cruz 11 Apr '12

11 Apr '12

Hi, Just wanted to drop a quick note to point out that in the last month or so I've noticed drawing with the calligraphy tool feels a lot faster. I'm using a build with optimizations turned off on OS X. I'm not quite ambitious to try a source control bisection to pinpoint when things got better. I wanted to be sure to say "good job" to all who keep helping.

1 0

Powerstroke: adding/deleting width nodes
by Johan Engelen 10 Apr '12

10 Apr '12

Hi all, I just fixed the biggest UI issue with powerstroke: adding and deleting control nodes. Now, you no longer have to unselect>select the path again. 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) If you find a bug or have a request, please add it to the bugtracker and assign to me. Do add a test SVG file if you report a bug! Cheers, Johan

1 0