August 2010 - Inkscape Devel - Inkscape Mailman

more UI mockups :)
by Alexandre Prokoudine 11 Aug '10

11 Aug '10

Hi, This time UI mockups come from Pablo Lizardo: http://www.flickr.com/photos/pablolizardo/4845828488/in/photostream/ http://www.flickr.com/photos/pablolizardo/4845888941/in/photostream/ Alexandre Prokoudine http://libregraphicsworld.org

4 4

Crashes
by Joshua A. Andler 11 Aug '10

11 Aug '10

Hey All, It seems like a decent number of tweets and complaints I've seen around the community (understandably) are about inkscape crashing. Doing basic searches for bugs tagged w/ crash gives the following info: All statuses is over 200 bugs and Confirmed or In Progress have 84. 84 crash bugs that can be reproduced seems unreasonably high for something intended for production work and code-wise there's a chance that some are caused by shared underlying issues. If anyone is interested in taking a look into these to see if there are any you might be able to fix, that would be awesome. http://bit.ly/InkCrash Cheers, Josh

4 12

Release Notes for 0.48: Connectors and Swatches
by Tavmjong Bah 09 Aug '10

09 Aug '10

Hi, There appears to be nothing in the release notes about the new Connector Tool additions. The Swatches section needs to be expanded with an explanation of how to use them. Why is a linear gradient created when clicking on the Swatches icon in the Fill and Stroke dialog? Tav

4 3

3D Box and 0.49
by Krzysztof Kosiński 08 Aug '10

08 Aug '10

Hello 3D Box is the main thing that prevents us from fixing the coordinate system bug. (The second thing are guides, but they're much easier to fix.) The reason is that it has a design fault - it stores perspectives and faces in desktop coordinates. A simple Y inversion does not fix the problem, because some code (e.g. default face coloring) is dependent on the chirality of the 3D coordinate system, and flipping the Y axis inverts the chirality. There's also a slew of other bugs related to 3D box in our bug tracker. What do we do with it in 0.49? I would really like to see the coordinate system bug fixed in 0.49, even if it means rewriting the 3D box from scratch, or even disabling it. Fancy features aren't very useful if we don't get the basics right. The issue of supporting legacy documents with 3D boxes is separate and I think it can be done if the 3D box gets rewritten first. We would just need to fix the document at load time. Initially I wanted to do this by direct XML manipulation before creating the SP tree, but now I see this has limitations - compatibility code at SP level is probably a better idea. Regards, Krzysztof.

2 1

inkscape aqua new build (-: PPC only )-:
by Drechsel Wolf 08 Aug '10

08 Aug '10

Hi everybody, as I upgraded my system to Mac OS X 10.5 "Leopard", I tried a new build of inkscape for native Mac OS X - called "aqua". Building didnt cause a lot of trouble, daring fellows can get it here: http:// verkehrsplanung.com/Inkscape-r9689-10.5+-PPC.dmg Attn.: It ist PPC only - dont waste your time, if you have an Intel machine. I couldnt do a lot of testing - but it looks as if it works quite nicely, but most of the well-known aqua bugs are maintained. To my feeling, it should not be so much work to get a really useable inkscape aqua - and I assume that many mac people would be happy with it. Sorry - I cannot do any coding - but will be happy to build and test everything. If somebody happens to have some spare time, he could have a look at: http://gtk-osx.sourceforge.net/ ige-mac-integration/GtkOSXApplication could be one topic to begin with. Else: Here is my bug-list - most of them are aqua-related: https://bugs.launchpad.net/~drechsel I'll continue praying every bedtime for a mac developer to care for inkscape aqua … (-; Greetings, Wolf Yours, Wolf

1 0

How to manage hundreds of bugs found by static analysis of Inkscape source?
by Vaughn Spurlin 05 Aug '10

05 Aug '10

I've used Coverity's static source code analysis tools to identify hundreds of bugs in Inkscape source. I'd like some guidance on the best way to contribute bug report details and proposed fixes to Inkscape. I'm a relatively new Coverity employee getting up to speed with our static analysis tools for identifying defects. Inkscape was recommended as an open source project with C/C++ source that I could use to satisfy my educational needs while contributing to an open source project. I want to contribute code fixes along with bug details. I suggest a first pass to report as many bugs as I can to the Inkscape Bug Tracker, followed by a second pass to add suggested fixes. Then Inkscape developers with commit privileges can review my code fix suggestions and apply the fixes as they see fit. Once the first pass is done and bug details are visible to the community, anyone else is welcome to contribute fixes also. What process should we follow to make the best use of everyone's efforts by avoiding several people working on the same bug? What I'm requesting at this point is a discussion about my suggestions, and some decisions about how best to proceed. As an example, here's one defect found by Coverity analysis, with my proposed code fix. CONSTANT_EXPRESSION_RESULT in /inkbugs/inkscape/src/main.cpp In sp_do_export_png(SPDocument *...): An operation with non-constant operands that computes a result with constant value (CWE-569). 1345 if (sp_export_area) { 1346 /* Try to parse area (given in SVG pixels) */ 1347 gdouble x0,y0,x1,y1; !sscanf(sp_export_area, &"%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) == 4 is always false regardless of the values of its operands (logical operand of if). 1348 if (!sscanf(sp_export_area, "%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) == 4) { 1349 g_warning("Cannot parse export area '%s'; use 'x0:y0:x1:y1'. Nothing exported.", sp_export_area); 1350 return; 1351 } fix noted 2010-07-25: 1348 if (sscanf(sp_export_area, "%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) != 4) { fix reason: sscanf returns the number of strings successfully scanned. The intent here is to ensure that all 4 input strings were scanned successfully. Vaughn Spurlin Coverity Technical Support

9 11

problem mit linien
by Christoph Grün 04 Aug '10

04 Aug '10

Hallo! Ich verwende Inkscape 0.47. Bei Inkscape 0.47 habe ich Probleme mit Linien. Sobald ich eine Linie dupliziere und mit der Maus/Pfeiltasten positionieren möchte, springt die Linie zu einer beliebigen XY Position auf dem Zeichenfenster. Es ist hierauf nicht mehr möglich, diese zu positionieren, auch bei Neustart von Inkscape ist das Problem vorhanden. Hat jemand dasselbe Probleme bzw. einen Lösungsvorschlag? Danke, Christoph

4 3

Problem compiling rev.9683
by LucaDC 04 Aug '10

04 Aug '10

On Windows XP SP3 I get this error while compiling: Make error line 299: problem compiling: src/extension/internal/emf-win32-inout.cpp: In member function 'virtual SPDocument* Inkscape::Extension::Internal::EmfWin32::open(Inkscape::Extension::Input*, const gchar*)': src/extension/internal/emf-win32-inout.cpp:2356: error: invalid conversion from 'int (*)(HDC__*, HANDLETABLE*, const ENHMETARECORD*, int, LPARAM)' to 'int (*)(HDC__*, HANDLETABLE*, ENHMETARECORD*, int, LPARAM)' src/extension/internal/emf-win32-inout.cpp:2356: error: initializing argument 3 of 'BOOL EnumEnhMetaFile(HDC__*, HENHMETAFILE__*, int (*)(HDC__*, HANDLETABLE*, ENHMETARECORD*, int, LPARAM), void*, const RECT*)' Of course, changing the definition: > myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD > const *lpEMFR, int /*nObj*/, LPARAM lpData) into > myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD > *lpEMFR, int /*nObj*/, LPARAM lpData) (taking away the 'const') fixed the problem but I'm not sure this is what was intended. Regards Luca -- View this message in context: http://old.nabble.com/Problem-compiling-rev.9683-tp29342879p29342879.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

4 5

FW: [cairo] EPS target: force boundingbox
by unknown＠example.com 04 Aug '10

04 Aug '10

Hi all, I sent a mail to Cairo's maillist about this issue: https://bugs.launchpad.net/inkscape/+bug/380501 Adrian Johnson provided a patch for Cairo that seems to solve our problem. How to proceed? Thanks, Johan > -----Original Message----- > From: Adrian Johnson [mailto:ajohnson@...1679...] > Sent: Tuesday, August 03, 2010 06:52 > To: Engelen, J.B.C. (Johan) > Cc: cairo@...278... > Subject: Re: [cairo] EPS target: force boundingbox > > On 16/07/10 21:47, J.B.C.Engelen@...1578... wrote: > >> -----Original Message----- > >> From: Adrian Johnson [mailto:ajohnson@...1679...] > >> Sent: 16 July 2010 14:00 > >> To: Engelen, J.B.C. (Johan) > >> Cc: cairo@...278... > >> Subject: Re: [cairo] EPS target: force boundingbox > >> > >> Cairo does not provide any means to override the automatically > >> generated BoundingBox comment. > > > > In that case, I want to file a feature request to either disable > > automatic calculation of boundingbox, or to provide a means to > > override it. > > Where should I file our request? > > > > Thanks, > > Johan > > The attached patch allows the cairo generated %%BoundingBox > and %%PageBoundingBox comments to be overridden using the > cairo_ps_surface_dsc_comment() API. > > eg > > surface = cairo_ps_surface_create() > cairo_ps_surface_dsc_comment(surface, %%BoundingBox: 100 100 > 200 200"); cairo_ps_dsc_begin_page(surface); > cairo_ps_surface_dsc_comment(surface, %%PageBoundingBox: 100 > 100 200 200"); > > Please test to see if this meets your requirements. >

4 4

New feature: Exchange position of selected objects
by Nicolas Dufour 03 Aug '10

03 Aug '10

Hi all, The patch provided in Bug #171944 "Exchange position of selected objects" (https://bugs.edge.launchpad.net/inkscape/+bug/171944) by Roland Meub is now in the trunk (committed revision 9681). It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the selected objects position: 1. according to the selection order, 2. according to the stacking order, and 3. clockwise. Please test and comment. Regards, -- Nicolas

1 0