- Inkscape Devel - Inkscape Mailman

New SVG compliance testing software
by Tomasz Boczkowski 13 May '14

13 May '14

Hi! Test case result images have been rated. In trunk at revision 13371 there are: 220 passes 126 fails 12 crashes In experimental branch revision 13356 there are: 221 passes 125 fails 12 crashes New pass is text-deco-01-b.svg Many thanks for Josh for help with rating unclear cases. Regards, Tomasz

1 0

Cache has performance issues
by Paul Kallnbach 13 May '14

13 May '14

Hi list A couple of weeks ago I posted a message regarding Inkscapes caching behaviour and also filed a bug report on launchpad (https://bugs.launchpad.net/inkscape/+bug/1267208). It turned out program response is far quicker with caching disabled in the source code. I'd happily provide a sample file or whatever is needed to visualize the described effect if requested. I think Inkscapes user experience could be noticeably improved by some simple modifications (e.g. an option to turn off caching via GUI) but in my opinion the caching systems needs quite a bit of refactoring. Unfortunately I lack the necessary insight and experience on the program to come up with a proper solution myself. I would be willing to give it a shot though if someone could point me to a good resource on how caching is designed and implemented (and would be willing to review my changes). With the new release coming closer I really hope somebody shows some interest in this. It does make a difference. Thanks. Paul

4 3

Oops,.. inkscape_r13349-201405111208
by Jelle Mulder 13 May '14

13 May '14

Hi Guys, When running Inkscape.exe on inkscape_r13349-201405111208 I just downloaded from the nightlies to give it a go and check the new LPE's I got nothing but a blinking cursor in a dosbox. That can't be the intention. However, I was wondering if I'd need anything special for this build I happen not to have. FYI running a win7 32 bit and this is a first for me. By the way I loved that new chamfer video and since I haven't been doing any testing for a while I'd love to get a go with the new toys. Many exiting changes that I am really looking forward to get to test. I am interested in doing a splash screen for the new release, but will need to know what the new stuff is, testing didn't get that far ;-) Keep up the good work! Cheers, Jelle

2 1

Starting the 0.91 Bug Hunt
by Bryce Harrington 13 May '14

13 May '14

For the Frost, one of our main activities is going to be the Bug Hunt. The purpose of the Bug Hunt is to improve our release's quality by tending to some of the many bugs people have reported in the past. Our first bug hunt focused on regressions found in 0.91. We still care a lot about regressions, of course, but this bug hunt is open season on ALL bugs ever reported. But reports about problems in the website, documentation, translation, packaging, admin, and codebase are all eligible targets, since every one of those areas is vital to achieving a high quality release. Only Wishlist bugs are omitted. The tally is taken of all bugs closed since the week Frost started (i.e. May 5th). 3, 6, 9, or 12 points are given for low, medium, high, and critical bug priorities respectively. +1 point will be given per year of age since the bug was filed, to encourage us to tend to older bug reports that have languished in the tracker. Points will be doubled for all regression-tagged bug reports, even if they were regressions in previous releases. A Bug of the Week will be announced each week, as we did in the last bug hunt. However, to switch things up a bit, I'm going to have the person who closed the highest total score of bugs in a given week be the person that selects the Bug of the Week for the subsequent week. Bryce

1 0

Possible bug compiling trunk
by Jabiertxo Arraiza Cenoz 13 May '14

13 May '14

Hi to all, i notticed a bug compiling in my machine, I'm compiling trunk in my Debian Jessie with gcc version 4.8.2. Show me this error: CXX libvpsc/solve_VPSC.o make[3]: *** No rule to make target '../../inkscape/src/libvpsc/csolve_VPSC.cpp', needed by 'libvpsc/csolve_VPSC.o'. Alto. make[3]: Leaving directory '/home/jtx/Development/inkscape/inkscape-gcc/src' Makefile:4790: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/jtx/Development/inkscape/inkscape-gcc/src' Makefile:991: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/jtx/Development/inkscape/inkscape-gcc' Makefile:686: recipe for target 'all' failed make: *** [all] Error 2 Thanks in advance, Jabier.

1 0

occasionally misleading file references in Merge requests.
by alvinpenner 13 May '14

13 May '14

this a source of some confusion, and also annoyance to me, so consider this to be a rant. I often try to see who has most recently changed a file, like guides_creator.py. So I end up at the address: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes?filter_fil… where it tells me that the file has been changed in rev 13007. So I click on that link, and it tells me that this rev actually changed this file, as expected. Then I see a Merge request in rev 13221, so I click on that link and discover that this particular file was not changed in that rev, even though the previous page said it was changed. Then I see a Merge request in rev 12404, so I click on that link and discover that this particular file was changed in that rev, as expected. So sometimes the file actually was changed and sometimes not. ............................................... Similar experience with file /src/extension/dbus/document-interface.cpp start at the location: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes?filter_fil… go to Merge request 12476 and discover that this file was not actually modified in this merge, nor in Merge request 13221, but it was modified in Merge request 13340 as expected. .............................................. this is very confusing. The problem seems to occur only in Merge requests. Does anyone know why some Merge requests lead to false references to file changes that never occurred? Cheers, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/occasionally-misleading-file-references-in… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 1

Problem whith multiple commit in experimental
by Jabiertxo Arraiza Cenoz 13 May '14

13 May '14

I do 3 commits instead one in experimental. I do whith a lot of care but my usual workflow of commit->merge->push isnt ok in shared enviroment. I think i realy need to use update->commit->push but cleaning for give this way to my first push, go wrong. The final push is ok. Sorry. Jabiertxof.

1 0

Circle Tool: How to Fix the Size
by Martin Owens 13 May '14

13 May '14

Hey Devs, I was working on an artwork[1] which needed specific sized segments using the circular tool. The problem is that there is no way to specify the size of an arc, just the start and stop degrees. What I need was a percentage value for size. I also found it impossible to adjust the arc's position. Object-Rotate puts the center inside it's bbox, not at the center of the arc. There's no key to press which could make both start and end nodes move together (that I know of). I ended up carefully adjusting start and end values together in increments. So. how could we design this tool to be better? Best Regards, Martin Owens [1] http://doctormo.deviantart.com/art/Imperial-and-Metric-Volume-453500628

1 0

64-bit: size of vectors and the like
by Johan Engelen 11 May '14

11 May '14

Hi all, TL,DR: please use std::size_t instead of e.g. unsigned int for STL's size() return values. A quick message. I just fixed a bug in buildtool.cpp that lead to an infinite loop when compiled for 64-bit. It happened because of a loop test on a string.size() with an unsigned int counter type. Changing the counter type to std::size_t fixed the issue. To be honest, I do not actually fully understand why it went into an infinite loop. But hope this is an example to motivate you to use the correct type to store / work with the result of STL's size() return parameters. Thanks, Johan

1 0

0.91 Release Notes
by Ryan Lerch 11 May '14

11 May '14

Just trying to get a go on this item in the release schedule [1] """ Identify remaining writing needed for Release Notes. """ Is it safe to start taking the release notes, and expanding them out further? Are all the features / bugfixes we want to document listed on the wikipage[2]? Or are there some that still need to be added? cheers, ryanlerch [1] - http://inkscape.org/en/develop/next-release/ [2] - http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91

5 5