September 2008 - Inkscape Devel

LPE Spiro stress test
by unknown＠example.com 03 Oct '08

03 Oct '08

Hi all, I think I just fixed the long standing bug where LPE Spiro crashed inkscape with a non-continuity exception. (we caught that exception, but okay...) I need some stress testing now! I already did some tests and am no longer able to crash inkscape. Give it a go and let me know if you can crash inkscape with lpe spiro now. Cheers, Johan

3 3

Cheat Sheet For Converting to 2geom
by Joshua L. Blocher 30 Sep '08

30 Sep '08

For those of you who asked and some who didn't. I give you a copy of my notes on converting from NR:: to Geom::. Please feel free to fill in anything I missed. I will update it with anything new I learn as time permits. http://wiki.inkscape.org/wiki/index.php/CheatSheetForConvertingto2geom Joshua L. Blocher verbalshadow

1 0

current problem with inkscape-svn & poppler-0.8.7
by unknown＠example.com 30 Sep '08

30 Sep '08

I upgrader last week poppler to version 0.8.7 and then get error on inkscape svn compilation, I suppose it's related to poppler upgrade instead of inkscape changes: ../../inkscape/src/extension/internal/pdfinput/pdf-parser.cpp: In member function ‘void PdfParser::doShowText(GooString*)’: ../../inkscape/src/extension/internal/pdfinput/pdf-parser.cpp:2264: error: no matching function for call to ‘GfxFont::getNextChar(char*&, int&, CharCode*, Unicode**, int*, double*, double*, double*, double*)’ /usr/include/poppler/GfxFont.h:204: note: candidates are: virtual int GfxFont::getNextChar(char*, int, CharCode*, Unicode*, int, int*, double*, double*, double*, double*) ../../inkscape/src/extension/internal/pdfinput/pdf-parser.cpp:2317: error: no matching function for call to ‘GfxFont::getNextChar(char*&, int&, CharCode*, Unicode**, int*, double*, double*, double*, double*)’ /usr/include/poppler/GfxFont.h:204: note: candidates are: virtual int GfxFont::getNextChar(char*, int, CharCode*, Unicode*, int, int*, double*, double*, double*, double*) warning: unused variable ‘nSpaces’ Here is the definition of this function in poppler/GfxFont.h: // Get the next char from a string <s> of <len> bytes, returning the // char <code>, its Unicode mapping <u>, its displacement vector // (<dx>, <dy>), and its origin offset vector (<ox>, <oy>). <uSize> // is the number of entries available in <u>, and <uLen> is set to // the number actually used. Returns the number of bytes used by // the char code. virtual int getNextChar(char *s, int len, CharCode *code, Unicode *u, int uSize, int *uLen, double *dx, double *dy, double *ox, double *oy) = 0; It looks like: the Unicode is a ** instead of a * (not sure, I have to look again on k&r & Stroustrup books as I didn't coded for long time) the int uSize is missing in the function call. Regards. Olivier

1 0

lpe vonkoch
by jf barraud 30 Sep '08

30 Sep '08

Hi! I did separate the "reference path" and the "generating path" in lpe-vonkoch. I think it makes the UI more clear, but it changes previous conventions of course (the last segment of the old generating path should be cut/pasted into the new "generating path"). Caution: this might change again. As it is supposed to contain only one segment, the "reference path" could/should be replaced by 2 points (on the other hand, it might be more convenient to be able to move both points at once, copy/paste that segment, etc..., so I'm not sure what's the best here). I also modified the tooltips, and parameter order, trying to follow your remarks. Thank you Alexandre P. and joncruz. Please review it again... Bye, JF.

1 0

Win32 nightly builds don't work since Aug 16
by Alvin Penner 29 Sep '08

29 Sep '08

this is just an attempt to bump the priority of https://bugs.launchpad.net/inkscape/+bug/259237 and http://sourceforge.net/mailarchive/forum.php?thread_name=op.uf6b2ds4a8nfnl%… as far as I can tell, the windows nightly builds have not worked since Aug 16. Using the Aug 21 download, the most recent timestamp that I can see on any files is 08/16/2008 02:49 PM 14,671,360 inkscape.exe part of my reason for posting this is because there is a possibility that I may have caused this, since I did a commit on that day, svn 19670, for the first time, and I'm afraid I may have done it wrong. -- View this message in context: http://www.nabble.com/Win32-nightly-builds-don%27t-work-since-Aug-16-tp1909… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

7 31

website
by Alexandre Prokoudine 28 Sep '08

28 Sep '08

Hi, Could we please have the website fixed? ./publish_web.sh does grab new stuff from SVN, but chnages on website do not appear. That's been happening for last couple of months. Alexandre

4 4

Fwd: NEW: Lots of stuff
by Pajarico 28 Sep '08

28 Sep '08

>> And even with that, it still doesn't recover >> zoom position. 3 works but ` doesn't. Maybe I'm doing something wrong. >> The equivalent menu option "Previous zoom" works, thought. > > Most likely your keyboard just issues some other keycode on pressing > this key. Again, it's only you who can investigate that and propose a > fix. > How can I check this? >> Actually a switch key would work better. Like push 3 for zoom in, push 3 >> again to zoom back. I don't like the idea of keeping Q stroked. > > That wouldn't work. We have much more zoom keys - 1, 2, 3, 4 etc all > have their functions. Not everyone zooms in with the intention to zoom > back again. If you want to zoom to selection _again_ and instead it > zooms you out to some previous zoom, it wouldn't be good usability. Maybe I didn't explain it correctly... I don't intend this to replace the zoom to selection button. Rather this is a new mode which would zoom in when pressed and zoom out when pressed again. The zoom in level would be detrmined by the largest zoom factor used on the last action, and the zoom out level would be determined by the smallest zoom factor used for a determined period of time (to avoid setting a zoom out level accidentally while zooming out with the wheel/zoom tool). The workflow would be like this: 1. You have an object and zoom in and do some fine tuning on the nodes. The zoom in factor is determined (and the zoom position). 2. You zoom back and stare at the changes for a while. In this short period of time the zoom out factor gets determined. 3. Press the key and you go back to zoom in state and do some more tweakings. 4. Press key again and go back to zoom out state. Stare at the editing and go back to zoom in if you wish. Something like this. Would be too cumbersome? > So, a single key which travels back through your history of zooms is a > much better solution. > That's kinda what I'm looking for... implementation details aside. Regards. PS: I'm resending this to inkscape-devel. Sorry bulia.

1 0

lpe point/path parameters incompatibility?
by jf barraud 27 Sep '08

27 Sep '08

Synopsis: Choose an lpe having both a point and a path among it's parameters. Apply it to an object. Node-edit the path parameter. Exit node-edit mode and move the object around. Inkscape crashes when you release the mouse. [ Program received signal SIGSEGV, Segmentation fault. 0x77c17742 in strcmp () from C:\WINDOWS\system32\msvcrt.dll ] You might complain there is no such lpe in the code base. hmmm. Right. This is a virtual bug (so very difficult to reproduce!), and the reason why I submit it here and not in launchpad. My new version of VonKoch would fit, but I don't want to commit it and get on all users nerves because of unexpected crashes... To make it less virtual, take lpe-test-doEffect-stack (an empty effect, good for testing) . -------------------- - in lpe-test-doEffect-stack.h, add #include "live_effects/parameter/path.h" ... PathParam path; - in lpe-test-doEffect-stack.cpp, add (in the LPE creator:) path(_("path param"), "tooltip of path parameter", "path_param", &wr, this,"M 0,100 100,0") ... registerParameter( dynamic_cast<Parameter *>(&path) ); -------------------- Is this the correct way to add a path parameter? When I do so, the bug shows up. If I comment out every thing about either the point or the path parameter, it works fine. When both are present it crashes (adding a redefinition of the path in a resetDefaults() function does not help) Am I missing something? any help/confirm/invalidate appreciated! Inkscapely yours, JF.

1 1

cmyk support in Inkscape/Cairo
by Felipe Sanches 27 Sep '08

27 Sep '08

what is the current status of cmyk support in inkscape? what about cmyk in cairo? I have a friend working on brazillian government and they seem to be interested in paying some brazillian developers to put some effort on cmyk support in inkscape Any suggestions about what should be preferably done? Would it be better to focus on cairo cmyk development? Which cmyk features are needed and currently not implemented? JucaBlues (Inkscape)

3 3

bbox not correctly calculated
by the Adib 27 Sep '08

27 Sep '08

Buliabyak, I refer to https://bugs.launchpad.net/inkscape/+bug/273767 If you select the shape in the attached file you get marker of a huge bounding box. It calculates a width of 83111 and a height of 18847. The calculated space for the image can not be given. BTW The same crash you get when you want to convert the object to bitmap. Despite the problem that it not properly handles NULL pointer after the g_new, could you please evaluate WHY it tells this huge bounding box? Regards, Adib. ---

1 0