- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] powerstroke
by Preben Soeberg 30 Sep '11

30 Sep '11

Oops Sorry, it's my mistake. Regards Preben > -----Original Message----- > From: Johan Engelen [mailto:jbc.engelen@...2592...] > Sent: 30 September, 2011 20:06 > To: Preben Soeberg > Subject: Re: [Inkscape-devel] powerstroke > > Are you sure? It should be all the way at the top "[Unstable!] Power > stroke". > > Ciao, > Johan > > > On 30-9-2011 6:59, Preben Soeberg wrote: > > Hm, Power Stroke disappeared from the LPE menu after the latest update. > > On XP r10654. > > In build.xml: #define LPE_ENABLE_TEST_EFFECTS 1 > > > > Regards > > Preben > > > >> -----Original Message----- > >> From: Johan Engelen [mailto:jbc.engelen@...2592...] > >> Sent: 29 September, 2011 23:40 > >> To: inkscape-devel(a)lists.sourceforge.net > >> Subject: Re: [Inkscape-devel] powerstroke > >> > >> On 21-9-2011 21:28, Johan Engelen wrote: > >>> On 21-9-2011 21:07, Josh Andler wrote: > >>>> Hi! > >>>> > >>>> Actually, perhaps we should enable all testing LPEs in trunk and only > >>>> disable what's "not ready" in the actual releases. What do others > >>>> think of this idea? > >>> Hm, while coding a bit on Powerstroke, I see that I am removing/adding > >>> parameters, which means that old powerstrokes no longer work (or, more > >>> precisely: partly work). > >>> If we enable the experimental LPEs in trunk, there should be a very > >>> clear indication that indeed they are experimental. > >> I just added PowerStroke to the normal nightly-build list of LPEs. I > >> settled for "[Unstable!]" in front of the LPE name, hopefully telling > >> people to use with caution, and not expect consistent behavior between > >> nightly builds... (should not be that bad, but might) > >> > >> Have fun fiddling with it. > >> Notes: Yes, it crashes Inkscape. Do not use on groups, do not use on > >> paths with multiple subpaths. If you delete a knot from the original > >> path, this will remove a segment and all strokewidth knots will move > >> accordingly to their new segment; the strokewidth knots are bound to a > >> segment number; when changing the number of segments, make sure that > all > >> strokewidth knots are bound to a segment number that will still exist > >> after your change. That is: when deleting one knot, make sure none of > >> the strokewidth knots are along the last segment; otherwise: crash. > >> Ctrl+click on strokewidth knot adds one. When adding/deleting knots, it > >> is best to reselect the path that you are working on; otherwise: crash. > >> Careful with the spiro interpolator; careful with any interpolator I > >> think; best to use the "Johan" one I guess... > >> See the attached file for some of my testcases. > >> > >> Ciao, > >> Johan > > > >

1 0

Increasing stroke width on grouped objects evokes erratic behavior
by Samuel Buttigieg 30 Sep '11

30 Sep '11

Hello fellow inkscapers, I am new to the scene in inkscape and i have been looking around for interesting bugs and I came across this one: https://bugs.launchpad.net/inkscape/+bug/734596 Does anyone have any extra information about this bug (code wise) as I am interested in working on this bug Best Regards, Samuel

3 4

inkscape + guile?
by unknown＠example.com 30 Sep '11

30 Sep '11

I'm interested in using Guile to write Inkscape extensions. I thought there was something like this around, but Google appears unwilling to provide me with a pointer. Is there an existing project for Guile extensions, or should I try my hand at it? -- Joakim Verona

2 2

Need Help
by paresh chaudhary 30 Sep '11

30 Sep '11

Dear Inkscape Team. There is one option (Object Properties) in Object menu of inkscape. Can we set common Properties of all object in layer. (With CTRL+A) i want to do that type of operation. Like in inkscape we can set color or text of all selected object. Waiting for reply as soon as possible *Regards, Chaudhary Paresh*

2 1

Re: [Inkscape-devel] Update on Diffusion Curves
by Jasper van de Gronde 29 Sep '11

29 Sep '11

On 2011-09-28 22:38, Sebastian Markbåge wrote: > On Mon, Mar 7, 2011 at 10:35 AM, Jasper van de Gronde > <th.v.d.gronde@...528... <mailto:th.v.d.gronde@...528...>> wrote: > ... > > I did a WebGL implementation of Jeschke's model last year. > > It did make me concerned about standardizing Diffusion Curves (such as > in SVG). > > Some artifact may not be visible in one implementation while it is > clearly visible in another. When rendering images designed using the > original tool by Orzan et al. I get some artifacts where the artist > have left imperfections. Those imperfections are not visible in > Orzan's implementation. Likewise, Jeschke's model hides other > artifacts that ARE visible in Orzan's model. > > http://labs.calyptus.eu/diffusioncurves/ > > What makes Diffusion Curves unique is that a small artifact can have a > huge impact on the over all image, as it's spread out by the solver. If you're talking about diffusion curves in the idealized sense, you are right that in principle all boundary points influence the entire image, but in practice the influence usually tapers off quite quickly. However, most solvers do have a bit of a problem with actually converging to a solution, which led me to my thesis subject. One problem is that all solvers tend to give smooth solutions that sort of look plausible, so it is not immediately obvious that something is wrong. In my thesis I describe a potential solution, by using a fundamentally different kind of solver, but it's definitely not a drop-in replacement for existing solvers (at least not yet). Another way of attacking the problem is to redefine diffusion curves to behave differently. Whether there is indeed a "better" definition is very much an open question. (I couldn't view your site btw, for some reason I can't get webgl to work, possibly because my notebook hardly has anything worthy of the name GPU.)

1 0

r10629: compiler warning and runtime error (EXC_BAD_INSTRUCTION, Illegal instruction/operand)
by ~suv 28 Sep '11

28 Sep '11

Revision 10629, compiling with GCC 4.2.1 on Mac OS X 10.5.8 (i386): 1) warning during compilation: > CXX xml/repr-css.o > xml/repr-css.cpp: In function ‘gchar* sp_repr_css_write_string(SPCSSAttr*)’: > xml/repr-css.cpp:235: warning: cannot pass objects of non-POD type ‘const class Inkscape::Util::ptr_shared<char>’ through ‘...’; call will abort at runtime > xml/repr-css.cpp:235: warning: format ‘%s’ expects type ‘char*’, but argument 5 has type ‘int’ 2) runtime error on launch (with new preferences file): > Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand. > sp_repr_css_write_string (css=0x5f74f70) at xml/repr-css.cpp:235 > 235 g_warning("sp_repr_css_write_string: %s %s", g_quark_to_string(iter->key), iter->value ); (full backtrace attached) 3) After changing line 235 to a static string: - launching Inkscape (with new prefs) reaches the g_warning() (on line 235) 133 times until the new document window is finally displayed - drawing a simple shape (rect) or a straight line (pencil tool) executes it 7 times, - changing the stroke width (via style indicator in the status bar) executes it 14 times -> I have reverted 'src/xml/repr-css.cpp' to r10628 for now. Questions: - Is this error related to using a rather old (or outdated) version of GCC on Mac OS X 10.5.8? (I don't have the option to use a more recent version for building Inkscape due to apparent ABI mismatches since all dependencies get built with Apple's GCC 4.0 (default compiler on 10.5.8)) - Is it expected that the warning on line 235 is reached so often while doing basic stuff like opening a new document window or drawing a simple object with default style attributes? ~suv (gdb) r Starting program: /Volumes/green/mp-inkscape/src/inkscape-trunk/Build/bin/inkscape Reading symbols for shared libraries ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++.......................................................................... done Xlib: extension "RANDR" missing on display "/tmp/launch-EhMYaX/:0". Reading symbols for shared libraries . done Reading symbols for shared libraries . done Reading symbols for shared libraries . done Reading symbols for shared libraries . done Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand. sp_repr_css_write_string (css=0x5f74f70) at xml/repr-css.cpp:235 235 g_warning("sp_repr_css_write_string: %s %s", g_quark_to_string(iter->key), iter->value ); (gdb) bt #0 sp_repr_css_write_string (css=0x5f74f70) at xml/repr-css.cpp:235 #1 0x0011ce3e in Inkscape::Preferences::mergeStyle (this=0x4448960, pref_path=@0xbfffe320, style=0x5f6d070) at preferences.cpp:501 #2 0x0053629c in sp_text_lineheight_value_changed (adj=0x725ca00, tbl=0x724bb48) at widgets/toolbox.cpp:6951 #3 0x04149f59 in g_closure_invoke () #4 0x0415c0d3 in signal_emit_unlocked_R () #5 0x0415d761 in g_signal_emit_valist () #6 0x0415da69 in g_signal_emit () #7 0x025fb38a in gtk_adjustment_value_changed () #8 0x02746bda in gtk_spin_button_set_property () #9 0x0414b7bb in object_set_property () #10 0x04151d6d in g_object_newv () #11 0x02a29719 in Glib::Object::Object () #12 0x0215962e in Gtk::Object::Object () #13 0x021c839e in Gtk::Widget::Widget () #14 0x021287aa in Gtk::Entry::Entry () #15 0x02187067 in Gtk::SpinButton::SpinButton () #16 0x0034c0df in Inkscape::UI::Widget::SpinButton::SpinButton (this=0x76120b0, adjustment=@0x7612090, climb_rate=0.10000000000000001, digits=2) at spinbutton.h:40 #17 0x0054e954 in createCustomSlider (adjustment=0x725ca00, climbRate=0.10000000000000001, digits=2) at widgets/toolbox.cpp:1053 #18 0x0007c352 in create_tool_item (action=0x7262608) at ege-adjustment-action.cpp:839 #19 0x025f5b28 in gtk_action_create_tool_item () #20 0x027f2b6c in update_node () #21 0x027f1d66 in update_node () #22 0x027f1d66 in update_node () #23 0x027f2daf in do_updates () #24 0x027f2e62 in gtk_ui_manager_real_get_widget () #25 0x00557f2a in setup_aux_toolbox (toolbox=0x45ff328, desktop=0x5f6fd80) at widgets/toolbox.cpp:1998 #26 0x00542365 in Inkscape::UI::ToolboxFactory::setToolboxDesktop (toolbox=0x45ff328, desktop=0x5f6fd80) at widgets/toolbox.cpp:1734 #27 0x0058838d in Inkscape::UI::UXManagerImpl::connectToDesktop (this=0x6f120a0, toolboxes=@0xbfffee84, desktop=0x5f6fd80) at ui/uxmanager.cpp:230 #28 0x004d3afb in SPDesktopWidget::createInstance (namedview=0x4a14600) at widgets/desktop-widget.cpp:1483 #29 0x004d3b49 in sp_desktop_widget_new (namedview=0x4a14600) at widgets/desktop-widget.cpp:1432 #30 0x000947d9 in sp_file_new (templ=@0xbfffefcc) at file.cpp:126 #31 0x00094b1c in sp_file_new_default () at file.cpp:178 #32 0x0000840b in sp_main_gui (argc=1, argv=0xbffff0fc) at main.cpp:974 #33 0x00008c8a in main (argc=1, argv=0xbffff0fc) at main.cpp:709 (gdb)

3 5

Advanced PDF export plugin for Inkscape?
by Donna Benjamin 26 Sep '11

26 Sep '11

I may have missed it... but is anyone here involved in this? Advanced PDF export plugin for Inkscape http://www.indiegogo.com/Advanced-PDF-export-plugin-for-Inkscape Just curious if this is coming from within the community, or anyone within the community knows about it - or it's a totally independent initiative? cheers Donna -- Donna Benjamin - kattekrab.net Inkscape: Open Source Scalable Vector Graphics http://www.inkscape.org

5 9

compiling inkscape
by Samuel Buttigieg 26 Sep '11

26 Sep '11

Hello all, I have a question perhaps someone of you can answer: Can inkscape be compiled in Kdevelop or do I have to use Eclipse? I tried various ways to get it to build in Kdevelop but so far they have failed. Searching on google did not provide any answers either, but there seems to be a lot of info about compiling inkscape in Eclipse. I mainly need the IDE to be able to debug inkscape source code that I am working on. Thanks and Regards, Samuel

2 1

compiler warning - value used in own initialization.
by Campbell Barton 22 Sep '11

22 Sep '11

Hi, noticed this compiler warning which looks like invalid code: src/gradient-drag.cpp:1894:69: warning: variable 'p' is uninitialized when used within its own initialization [-Wuninitialized] `bzr blame` points to - 10582.1.11 tweenk. This is the line: Geom::Point p = ls.pointAt(ls.nearestPoint(dragger->point + p)); -- - Campbell

1 0

ssh access to inkscape.org
by Alexandre Prokoudine 21 Sep '11

21 Sep '11

Hi again, Folks at OSUOSL tweaked various things here and there recently, so SSH might not like your public key now. The fix is to mail support at osuosl and attach your current public key (no need to create a new one). Just so you know. Alexandre Prokoudine http://libregraphicsworld.org

1 0