November 2015 - Inkscape Devel

Measure and Spray tool
by Jabiertxo Arraiza Cenoz 08 Nov '15

08 Nov '15

Hi to all, the spray tool and measure tool improvements are now in trunk, thanks to Nathan Hurst and Mc- for the fast reviews and to all people involved on it. Bug report it! Regards, Jabier. https://www.youtube.com/user/jabiertxof/videos

3 2

Screen tearing on Inkscape (OS X)
by Papoj Thamjaroenporn 08 Nov '15

08 Nov '15

Dear Inkscape-devel, I recently picked up Inkscape again, and there is this screen tearing <https://en.wikipedia.org/wiki/Screen_tearing> issue I have seen on OS X, and I am wondering what the causes are and how I may be able to contribute. As far as I understand, screen tearing seems to be an issue specific to GTK2. This happens when I scroll or zoom the canvas, where screen refresh rate is not synced with canvas rendering. This happens either on X-based version (I tried using the official Inkscape app) or Quartz-based version (I tried by compiling the trunk using Quartz variants). I also found that ~suv has this exciting development on native OS X integration with GTK3. The artifacts I have seen are exactly like in this screen recording <https://inkscape.org/en/gallery/item/4556/> of Inkscape with GTK2 that ~suv posted. So, am I correct to say that GTK3 somehow eliminates this problem, even without native OS X integration? How does it do so? If we stay with GTK2 as of now, is there a way to fix the tearing issue? Regards, _______________________ Papoj "Hua" Thamjaroenporn papoj@...3117...

2 2

Re: [Inkscape-devel] Board Meeting @ Friday Nov 6th, 2015
by Bryce Harrington 06 Nov '15

06 Nov '15

Reminder that the meeting is tomorrow at Noon Pacific time. Check your times since daylight savings is in effect. Last month's meeting log is posted here for reference: https://inkscape.org/en/gallery/item/6701/ Bryce On Thu, Oct 29, 2015 at 08:27:15PM -0700, Bryce Harrington wrote: > Hi all, > > Last month's meeting went well, and we decided to have another in early > November at a similar time and place. > > We'll be holding an Inkscape Committee meeting on Friday the 6th of > November, on #inkscape-devel, at 1900 UTC (Noon PDT / 9pm CEST) > > http://wiki.inkscape.org/wiki/index.php/Board_Meetings > > Agenda is: > > * Code of Conduct & Privacy Policy > * Funded development > * GSoC 2016 > * Fiscal Sponsorship Agreement (FSA) > * Hackfest 2016 > * Budget 2016 > * Other business > > Bryce > > ------------------------------------------------------------------------------ > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 1

Notifying users of nonfatal errors, general interface?
by mathog 05 Nov '15

05 Nov '15

Hi, All, I posted about this back on 2015-03-26 with the title Example of Inkscape handling corrupt input file but there were apparently no responses. So once again, is there an interface in Inkscape where code can push a message for a nonfatal event such that: 1. In GUI usage - a pop up appears with the message. 2. Command line/filter usage - message is sent to stderr Usage example: SVG -> EMF export cannot handle opacity because the output format does not support it. The code currently just drops the opacity property which of course results in output visually different from the original (although all the same elements are there). End users keep tripping over this, example: https://bugs.launchpad.net/inkscape/+bug/1513262 So I would like a warning message to appear. Ideally this would show up in the code as something really simple like this: if(errors_found){ inkscape_display_message(my_message): } and then this function/method would go on and never has to do anything else related to that message. If there is already a function/method corresponding to "inkscape_display_message", what is it called? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

1 0

Suppressing specific Unknown Attribute '__alloc_size__' warnings
by Papoj Thamjaroenporn 05 Nov '15

05 Nov '15

Dear Inkscape-devel, I became tired of seeing these same warning messages over and over again whenever I compile and debug the code: /opt/local/include/gc/gc.h:804:23: warning: unknown attribute '__alloc_size__' ignored [-Wunknown-attributes] GC_API GC_ATTR_MALLOC GC_ATTR_ALLOC_SIZE(1) void * GC_CALL For the record, I compile Inkscape 0.91(trunk) with XQuartz backend using latest clang from Xcode. Someone also has seen <https://answers.launchpad.net/inkscape/+question/256081> this before (I’m glad the instructions I posted on the mailing list a year earlier were useful :-)), and the thing about warnings was ignored because the issue there was about getting the code to run. It seems that clang has removed alloc_size attribute <https://github.com/neovim/neovim/issues/429> a while ago. But these warnings would pop up about gazillion times per compiling session, from gc.h, so I am wondering if I can suppress this warning specifically. I’m not familiar with how to add a suppression in autoconf. Do I just do the following in configure step? ../trunk/configure --prefix=YOUR_BUILD_DIRECTORY --disable-static --enable-shared CC="clang" CXX="clang++" CXXFLAGS="-std=c++11 -stdlib=libc++ -I/opt/local/include -Wno-unknown-attributes" CPPFLAGS="-I/opt/local/include -U__STRICT_ANSI__ -Wno-unknown-attributes" If I re-configure the build, do I have to run "make install" again before "make -j 4"? I’m also not sure if globally suppressing this kind of warning is recommended. I have not seen this kind of warning other than this, and I couldn’t even find its definition on the official Clang documentation <http://clang.llvm.org/docs/UsersManual.html>. If this is not recommended, does anyone know how I can specifically suppress this particular warning? Regards, _______________________ Papoj "Hua" Thamjaroenporn papoj@...3117...

4 5

Absolute path to image
by my369 04 Nov '15

04 Nov '15

Hello. I have noticed sucha feature in inkscape, every time I press the "Extract Image.." path for all images will change to absolute. It's either something I do not know, or it is a bug.

2 1

question about nodes display
by Brynn 02 Nov '15

02 Nov '15

Hi Friends, I sent this message earlier, but the attachment has apparently put it over the size limit. So it's waiting for a moderator, for now. But perhaps could be answered without the PNG. So just in case, here's the message, and if the screenshot is needed, I'll try to figure some way to send it. Original message below: This is something I noticed a long, long time ago, and never really questioned. But now I'm writing a tutorial about node editing, and it seems a good time to find out. When more than 1 node are all stacked up, precisely on top of each other -- if it's an even number of nodes, then they appear to be smaller than a regular node. (see in the top aqua circle in the attached ne12.png) It's what you see if you use "Break path at selected nodes". But if there are an odd number of nodes all stacked up, it looks just like a regular node. So there's no visible clue -- you only know how many nodes might be there, if you happen to select them (by dragging a selection box around), or if you already know, or happen to remember what's there. I'm curious why it's made that way, and whether it might be helpful if any number of stacked up nodes can look like the even number of stacked up nodes (just a smaller node). Well, I would find it helpful anyway, and wonder if others might as well. I'd appreciate if anyone can explain. Thank you very much, brynn

3 5

question about nodes display
by Brynn 01 Nov '15

01 Nov '15

Hi Friends, This is something I noticed a long, long time ago, and never really questioned. But now I'm writing a tutorial about node editing, and it seems a good time to find out. When more than 1 node are all stacked up, precisely on top of each other -- if it's an even number of nodes, then they appear to be smaller than a regular node. (see in the top aqua circle in the attached ne12.png) It's what you see if you use "Break path at selected nodes". But if there are an odd number of nodes all stacked up, it looks just like a regular node. So there's no visible clue -- you only know how many nodes might be there, if you happen to select them (by dragging a selection box around), or if you already know, or happen to remember what's there. I'm curious why it's made that way, and whether it might be helpful if any number of stacked up nodes can look like the even number of stacked up nodes (just a smaller node). Well, I would find it helpful anyway, and wonder if others might as well. I'd appreciate if anyone can explain. Thank you very much, brynn

1 0

Spray Tool V
by Jabiertxo Arraiza Cenoz 01 Nov '15

01 Nov '15

Hi again, another video to the list. Sorry for the multiple steps, but my initial objetive increase in each video. Next time I try to reduce the number of videos to one or maybe 2. https://www.youtube.com/watch?v=Zn3vzf-yA_w Whith this improvement, now the Spray tool get the trace dialog options if in "pick" mode. Cheers, Jabier.

1 0