- Inkscape Devel - Inkscape Mailman

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

Re: [Inkscape-devel] Spray Tool Improvements III
by Jabier Arraiza 30 Oct '15

30 Oct '15

Hi Ivan, put reply on list. First one is not posibol to put them "exactly" because is based on a random algoritm of the tool. Second one: Great idea!!! I try to implement. Thanks for the feedback! El jue, 29-10-2015 a las 12:15 +0100, ivan louette escribió: > Then what do you think of the two following ideas : > > 1° spraying exactly contiguous squares or quadranglesto simulate > bitmaps ? > > 2° spraying objects which increase or decrease in size based on the > darkness or lightness of the background colors ? > > Le 29/10/15 11:23, Jabier Arraiza a écrit : > > Yes Ivan!!! > > > > El jue, 29-10-2015 a las 09:14 +0100, ivan louette escribió: > > > Can you spray over a bitmap image and acquire its colors like > > > this is > > > possible with clones ? > > > > > > Le 28/10/15 21:10, Jabier Arraiza a écrit : > > > > Thanks Ivan, this allow a lot of posibilities, because the > > > > color > > > > that > > > > change is only the fill, the stroke retains original color, so > > > > you > > > > can > > > > do things like this: > > > > http://i.imgur.com/wn7n95Z.png?1 > > > > > > > > Regards, Jabier. > > > > > > > > > > > > El mié, 28-10-2015 a las 20:53 +0100, ivan louette escribió: > > > > > Amazing ! I easily imaginate it combinated with some svg > > > > > filter > > > > > to > > > > > simulate organic cellular textures ! > > > > > > > > > > ivan > > > > > > > > > > Le 28/10/15 19:31, Jabier Arraiza a écrit : > > > > > > Hi again, my last video about new features to the spray > > > > > > tool: > > > > > > https://www.youtube.com/watch?v=aTdKu7mAZE8 > > > > > > > > > > > > Thanks to Gabriel Grosso for the idea and to Mc for his > > > > > > help on > > > > > > review. > > > > > > > > > > > > Cheers, Jabier. > > > > > > > > > > > > > > > > > > --------------------------------------------------------- > > > > > > ---- > > > > > > ---- > > > > > > ------------- > > > > > > _______________________________________________ > > > > > > Inkscape-devel mailing list > > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > ----------------------------------------------------------- > > > > > ---- > > > > > ---- > > > > > ----------- > > > > > _______________________________________________ > > > > > Inkscape-devel mailing list > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

3 5

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 113, Issue 19
by Jelle 30 Oct '15

30 Oct '15

Great work guys! The spray tool improvements make it a lot more useful, but the text improvements are a bit of a breakthrough. Thanks for all the great effort. > 1. New branch SprayTool Improvements > 9. Vertical text & 'text-orientation' Cheers, Jelle

2 1

Recent changes that would result in object reordering???
by mathog 29 Oct '15

29 Oct '15

I fixed a bug today and found that the emf round trip test no longer worked. (This has nothing to do with the bug I was working on, which just changed a couple of scale factors related to dashed lines.) The round trip test works like this (sorry about the wrap): $INK --file=/usr/local/src/libUEMF/dist/test_libuemf_ref.emf --export-emf=/tmp/test1.emf $INK --file=/tmp/test1.emf --export-emf=/tmp/test2.emf $INK --file=/tmp/test2.emf --export-emf=/tmp/test3.emf $READEMF /tmp/test1.emf > /tmp/test1_emf.txt $READEMF /tmp/test2.emf > /tmp/test2_emf.txt $READEMF /tmp/test3.emf > /tmp/test3_emf.txt afterwards "diff" of any of pair of the test*_emf.txt pairs would show only the one line associated with the name change. Not anymore though. Now they differ from each other a lot. When the emf files produced are viewed in inkscape they appear to be the same. However, the text dumps of the EMF files are wildly different, apparently because the object order is no longer the same. That is, the input stage is seeing the objects in one order, and the output stage is seeing them in another. The reordering seems to be repeatable, that is, if test1.emf is loaded and saved as test9.emf, then the text dump of that is the same as test2.emf (other than the file name field.) The same test with WMF is still stable, but that is a much, much simpler and smaller test file. What has changed in Inkscape that would be causing this? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

3 3

Code of Conduct review
by Krzysztof Kosiński 29 Oct '15

29 Oct '15

Hello I think the CoC can be considerably improved. I think it's too wordy in a few places. Here is my proposed revised text. Inkscape online communities are intended to be a friendly, inclusive spaces for users to collaborate on the further development of Inkscape, share and discuss their creations, inspire each other and interact in constructive ways. To that end, we have established a set of guidelines that we believe will help foster such an environment. Anyone willing to follow these guidelines is welcome. In your interactions with others, please do your best to: - Be respectful. There's always a human very much like you at the other end. Always treat them respectfully and be kind to them, even if you disagree with them. - Be responsible. Everyone makes mistakes from time to time; own up to them and be willing to work on fixing them. If someone has been harmed or offended, listen carefully and work to right the wrong. - Don't take criticism personally. Remember that criticizing an idea (e.g. a technical proposal or an user interface blueprint) is different from criticizing the person that proposed it. Do not become overly attached to your contributions and do not demand preferential treatment for them because of your standing in the community. Ideas should stand on the merit of their supporting arguments, not on the merit of their originators. - Use neutral language. Avoid words that others are likely to find offensive or excluding. - Forgive. If someone wronged you and apologized, do not keep demanding special punishment. Don't hold a grudge or seek to settle scores. Be willing to let things slide if it benefits the community. - Give credit where it is due. Never try to pass off others' work as your own. - Disclose and address conflicts of interest. You should be aware when you are conflicted due to employment or other projects you are involved in, and abstain or delegate decisions that may be seen to be self-interested. When in doubt, ask for a second opinion. - Step down considerately. When you leave a responsible position in the Inkscape project, do so in a way that minimizes disruption to the community. Tell people you are leaving and take the proper steps to ensure that others can pick up where you left off. The following actions and behaviours are deemed unacceptable: - Harassment of other users, including but not limited to threats of any kind, insults, discriminatory language and jokes, unwelcome sexual attention, posting personally identifying information ("doxing"). - Deliberate disruption: trolling, spamming, flaming, baiting, attention seeking, distribution of malware, any kind of attacks against Inkscape computing infrastructure or that of its parent organizations. - Distribution of illegal or pornographic material in Inkscape communities. - Advocating or encouraging any of the above. If you believe a member of an Inkscape community is in breach of the above code, report it to the appropriate moderators (contact info here), even if you are not among the directly affected parties. Violations of the code can be met with disciplinary action, ranging from a private warning to complete, permanent expulsion. If you feel you have been unfairly accused or penalised, you may contact Inkscape's board (link to governance section here). Decisions of the board are final. Summary of changes: I removed some text that I felt was repetitive and split the code into 2 sections with desirable and undesirable behaviors. I also added 2 points: "Forgive" and "Give credit where it is due", which I think are pretty important, and a paragraph at the end about disciplinary action. Best regards, Krzysztof

5 11

Spray Tool Improvements III
by Jabier Arraiza 28 Oct '15

28 Oct '15

Hi again, my last video about new features to the spray tool: https://www.youtube.com/watch?v=aTdKu7mAZE8 Thanks to Gabriel Grosso for the idea and to Mc for his help on review. Cheers, Jabier.

3 3