March 2008 - Inkscape Devel - Inkscape Mailman

Windows Dev Build Feb 26 08 - improvements and problems...
by rygle 01 Mar '08

01 Mar '08

Hi, Just writing with some experiences of the latest Dev build for windows. 1. It seems to be rendering a bit faster lately. Probably due to Bob's hard work with dll's and the latest Cairo. Thanks! 2. PDF output seems to be doing gradients and transparency quite well (as vector art not raster), which is great :-D, but still not blurs :-((. Again probably due to Cairo improvements. Getting close! 3. The windows dialogues have kicked in I notice. Trying to view a thumbnail causes a crash on my system. I also miss the GTK ability to store your own folder shortcuts on the side. Have to find some windows program to do that! 4. With the windows dialogues (or perhaps related to Alexandre's changes - see http://www.nabble.com/Regarding-WMF%2C-PS-based-AI%2C-SK-and-FIG-files-supp… here ) the saving sequence seems to be messed up. 4a. If I select save as PDF via Cairo, it goes for the selection immediately below, which is PS. If I select EMF, it saves it as POV. Whatever I want, I have to go for the one above, but you can't now re-select Inkscape SVG. Always one step below, unless I just hit save, which does whatever was last without problem. 4b There's a weird loop going on when saving, which I think is related to the bug above. See my comment at step 4 below. 1. Save something as an Inkscape SVG (default). 2. Save as PDF or whatever else. 3. Save again as Inkscape SVG and try to close Inkscape. 4. Inkscape complains 'The file "{filename.svg}" was saved in a format that may cause data loss! Do you want to save the file as an Inkscape SVG?' options - Close Without Saving, Cancel, Save as SVG. (I think this is caused because now when you select Save As -> Inkscape SVG, you're actually choosing Plain SVG (the one below), which Inkscape thinks will cause data loss). 5. Click ' Save as SVG' 6. Back to step 3 and infinite loop - must select 'Close Without Saving' to escape the loop. Obviously some good steps forward have been made, but a few minor problems have crept in. I hope this is helpful. Rygle. -- View this message in context: http://www.nabble.com/Windows-Dev-Build-Feb-26-08---improvements-and-proble… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

7 14

Change to NRRect
by Jon A. Cruz 01 Mar '08

01 Mar '08

I just did a change to NRRect's default constructor. Prior to this it was leaving all of its members uninitialized, and valgrind found that some like this were being checked for 'empty'. So random behavior could have been seen. I also did a fix under display, but that was an array index going below zero, but I think the loop would have exited anyway, so I don't expect that change to really affect the program. I'm mainly concerned that some bugs might have been caused by 'new' NRRect variables being seen as non-empty and now they'll show up as empty. BTW, these were the first two things I found by getting to run under Valgrind and seeing what was reported right off the bat. I'll probably try to actually explore the app a little more under valgrind, but I think these two were a good start.

2 2

Re: [Inkscape-devel] Extensions on win32
by Aaron Spike 01 Mar '08

01 Mar '08

Simon Mieth wrote: > Aaron Spike schrieb: >> Simon Mieth wrote: >>> Windows XP SP2, Inkscape daily build from Feb 29 2008: >>> Java extension and .NET error message >>> >>> Microsoft Visual C++ Runtime Library >>> Runtime Error! Inkscape internal error >> >> This must be a new issue. Could you please make a backtrace with gdb >> (there should be instructions on the wiki or website) and post a bug >> on launchpad? >> >> Aaron Spike >> > Ok I will try this. Thanks

1 0

assert_close
by bulia byak 01 Mar '08

01 Mar '08

Back in 2004, Peter Moulder added assert_close to nr-matrix.cpp and used in it several matrix operators in libnr (such as multuplying a matrix by a scale, etc). All it does is just checks if two matrices are "close enough". I am going to remove this assert because: - what it tests is simply computer arithmetic, not something Inkscape itself can get wrong. I don't think it can discover any bugs for us. - used in basic operators, it likely slows the program down for no gain whatsoever. Unless there are objections, of course. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

guidlines warning
by Jon A. Cruz 01 Mar '08

01 Mar '08

Not sure if this actually affects anyone, but I ran across a clump of warnings display/guideline.cpp: In function ‘void sp_guideline_render (SPCanvasItem*, SPCanvasBuf*)’: display/guideline.cpp:140: warning: passing ‘double’ for argument 3 to ‘void sp_guideline_drawline(SPCanvasBuf*, gint, gint, gint, gint, guint32)’ ... eight of those in a row. I'll be fixing them.

1 0