December 2007 - Inkscape Devel

Collaborate
by Daniel Garcia Moreno 05 Dec '07

05 Dec '07

Hello, first of all, thanks, I use inkscape since some years, and I love it, thaks for this excellent tools that you are making, it's amazing. I'm a programmer and I want to collaborate in this project. I am looking for a list of bugs, for write some patch, look the code and learn about the code. If you could tell me some easy bug to fix, I can write some code.

3 2

using LPEs
by Steren Giannini 05 Dec '07

05 Dec '07

hello, I made recently my first draw using Live Path Effects. (see http://pannini.lesgeorges.org/media/couv_web.png) And I can tell : they are very powerful ! I wrote the main points that need to be corrected or at least discussed. I know LPEs are not finished yet, but I want to be sure that those points are taken into account. - I had a problem when I wanted to copy a path with a pattern along path applied : the "pattern source" is not copied but the two paths share the same "pattern source". If I want to modify the pattern source of my copy and not disturb the first one, I can't. To my opinion, this is really something to change. - The same problem for the "bend path" effect - In the last SVN, when you translate a object with a "bend path" effect, it translate well. But I really think that when rotating or scaling such kind of object, it should do the same : rotate and scale the "visual object" (maybe by rotating or scaling the "source path" too) - scaling or flipping an object with a pattern along path effect applied : the source path is modified but not the "pattern source" => the "visual object" shape is not the same than before the transformation. ( see : http://pannini.lesgeorges.org/media/flip_prob1.png) Steren

3 3

Redo problem, element created without "id" attrib
by unknown＠example.com 05 Dec '07

05 Dec '07

Hi all, I have a problem that I do not know how to fix. When a grid is created and then Undo is pressed, things work great. However, then "redo" crashes inkscape (when grid tab of document properties is open). This is because of the following reason: when redo is done, a new child is added to sodipodi:namedview, this triggers updating of the documentproperties gridpage. However, at that time, the "id" attribute of the child has not been set yet. (I don't know at what time it is set, but sp_namedview_child_added is called with a child that has no 'id' attribute! This attribute is needed, because it provides the grid's name to put in the tab in the dialog. I'd like to know how I should solve this (i.e. obtaining the 'id' attribute when a 'redo' action is performed). Thanks! Johan

1 0

new stock patterns and screenshot
by bulia byak 04 Dec '07

04 Dec '07

I added a few basic stock patterns and made a screenshot: http://www.inkscape.org/screenshots/gallery/inkscape-0.46-stockpatterns.png enjoy :) -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

NEW: Grid visibility and snap enabling
by unknown＠example.com 04 Dec '07

04 Dec '07

Hi all, I just added two checkboxes to the grid settings: * Visibility and snap enabled. ** Visibility turns of display of the grid, which I find useful from time to time because snapping is still enabled for invisible grids. To disable snapping (when having multiple grids, this is essential), one should use 'snap enabled' ** "Snap enabled" does not yet work. I hope Diederik can implement this soon, I think it should not be too hard? * I hope to get the axonometric grid working soon, I need it at work! :-) * I am aware of the bugs in setting grid parameters. Hopefully I can find the cause soon, it is annoying me aswell. Cheers, Johan

7 13

Launchpad Tips & Tricks: Upstream Bugs
by Bryce Harrington 04 Dec '07

04 Dec '07

Being able to track upstream bugs is (IMHO) one of the best features of Launchpad from Inkscape's perspective. Let's take a look at how this works: First, we find a bug that is really an upstream issue. Here we go: Main window disabled if a modal dialog sinks https://bugs.launchpad.net/inkscape/+bug/168301 This is related to the infamous "dialogs not on top with Win32" problem that we know stems from Gtk, but with an unfortunate twist - if the application is minimized and you right click "close", you never see the dialog, but since the dialog is modal, you can't restore it! Feh Win32! Actually, it's a Gtk problem. So next we go to the gtk bug tracker. >From gtk.org I clicked on "Bug tracker", then went to bugzilla.gnome.org. I find the search box and enter "windows dialogs". Browsing through the list I spot this one: Bug 169965 -- transient dialogs with minimized parent http://bugzilla.gnome.org/show_bug.cgi?id=169965 [Note, all gtk bugs are also imported into Launchpad at https://bugs.launchpad.net/gtk/, which would probably be easier to search...] Reading the bug, it looks like this describes our issue. Unfortunately, the bug hasn't received much activity over the past year (we'll address this in a bit), but at least it's known... Now go back to our Launchpad bug: * Look at "Also affects: +Project... +Distribution/Package..." * Click on "+Project" * Type in "gtk" and hit Continue * For the URL, cut and paste the bugzilla.gnome.org bug URL there * Click "Add to Bug Report" Now our bug report shows the link to the upstream bug. Periodically (once a day I think), Launchpad will spider bugzilla.gnome.org and grab any status changes to the upstream bug report and notify us if the status changes. So in the future when people look at this bug, they'll be able to immediately see if/when it's fixed upstream. We're not done yet though! Let's be good citizens and let upstream know we also experience this problem. I log into my bugzilla.gnome.org account, and add a comment to the above bug: "I think we're also experiencing this bug with Inkscape on Windows. A user reports... https://bugs.launchpad.net/inkscape/+bug/168301 [Pasted copy of original report from our end] Has anyone had a chance to look into this?" This will both ping upstream about the issue (hopefully raising its importance, maybe triggering them to update the bug report if it's already fixed, or a dupe), and give the extra info to help debug it. If we had failed to find a matching bug upstream, we should report a new one. If you're unsure, it's sometimes better to report a new one and let them dupe, than to incorrectly attach our bug to a wrong report, but use best judgement there. Now go to https://bugs.launchpad.net/inkscape/ and look for the link "0 bugs fixed elsewhere". When our upstream bug gets fixed, this link will change to "1 bug fixed elsewhere", which will let us see the bugs fixed by our upstreams. :-) Notice the URL for this search says "...=resolved_upstream". If we change this to "open_upstream", we can see the bug we just linked: https://bugs.launchpad.net/inkscape/+bugs?field.status_upstream=open_upstre… Some Homework: In my gtk bugzilla searches, I ran across a couple related bugs, which sound similar to other issues we have in Inkscape. See if you can find our matching reports, and link them up: Bug 164537 -- Non-modal transient dialogs should iconify with parent http://bugzilla.gnome.org/show_bug.cgi?id=164537 Bug 171456 -- "Keep Above" option in Gimp broken on Win32 http://bugzilla.gnome.org/show_bug.cgi?id=171456 Bryce

1 0

Inkscape bugs status
by Bryce Harrington 03 Dec '07

03 Dec '07

1 0

Launchpad Tips & Tricks: Duping Bugs
by Bryce Harrington 03 Dec '07

03 Dec '07

It's good to see all the people giving Launchpad a try, and discovering both its cool bits and some frustrating bits. For those who are finding some irritations, please give it some time - when I first started using it, I also found the interface to be unintuitive in places; I'm hoping the tips and tricks I'm posting will help. Here's half a dozen tips related to bug duping: 1. Adib asked about how to dupe bugs. This falls into the cool feature category, but the links may not be where you expect. When viewing a bug, "Mark as duplicate" is in the Actions list on the left. From there, you can indicate the bug id number that this is a duplicate of. 2. The bug report will clearly tell you that there are dupes of a given bug, or that the bug is a dupe of such-and-such other bug. For bugs with dupes, there is also a listing of its dupes - this can be found on the left column in an expando-box titled "Duplicates of this Bug". 3. When a bug is marked as a dupe, it no longer shows up in searches, which is nice. But you can still get to it either directly by ID, or via the link in the parent bug. 4. People who were subscribed to the dupe bug will now receive the update notifications from the parent bug. This is usually useful, but keep it in mind if commenting on a bug with a large number of dupes that you're not spamming everyone with trivialities. 5. Note that it's not possible to mark a bug a dupe if it also has dupes attached to it. You have to individually move the dupes to the parent. Sort of annoying, but it's rare when you need to do this. 6. When closing a bug that has dupes, it's good practice to review each of the dupes and check that the solution definitely does account for all those reported problems. I was at first annoyed to find endless duplicate reports of bugs, as it seemed like a waste of effort that could be avoided if the reporter searched the existing bugs. However I've since changed my mind, for a few reasons. First, (at least for xorg) most users don't have enough knowledge to really know for certain that their problem matches someone else's, so it usually requires an expert to verify that the issue really is a dupe. Second, from a workflow perspective, finding/marking dupes is much more straightforward than trying to untangle a bug report that contains multiple unrelated issues in it. Third, a bug report with a lot of dupes typically ends up being easier to gain a fix than one with no dupes - both because it emphasizes the importance of the bug, and because the "many eyes" effect starts kicking in, and people subbed to the bug through dupes can start sharing ideas and findings with each other. So, I generally encourage tell reporters, "If you're concerned that your bug report might be a dupe but you're not sure, report it as a separate bug, and just say in your report 'might be related to bug xyz'". This saves the bug triager time of tracking down potential matches but still lets your issue be handled even if it's unrelated. Bryce

1 0

Inkscape native on OSX - try 2
by jiho 03 Dec '07

03 Dec '07

Hi everyone, I've been trying to get Inkscape to compile against the new version of GTK on OS X, with the "quartz" option enabled (i.e. without X11). The good news is that it compiles and that MacPorts provides a way to work with both native and X11 versions of GTK quite easily (which means one does not have to remove and recompile everything one way or another every time). The bad new is that, though Inkscape starts without X11 and that the GUI is shown, it crashes with this error message: ** (inkscape:9060): CRITICAL **: const GSList* sp_document_get_resource_list(SPDocument*, const gchar*): assertion `document != NULL' failed ** (inkscape:9060): CRITICAL **: const GSList* sp_document_get_resource_list(SPDocument*, const gchar*): assertion `document != NULL' failed Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. (inkscape:9060): GLib-WARNING **: g_main_loop_run(): called recursively from within a source's check() or prepare() member, iteration not possible. Any idea from where than may be coming from? It doe not occur with the X11 version so that's probably related to GTK/Cairo/Pango/Poppler being freed from X11. However, the GUI shows and the messages don't seem directly display-related. Is that a GTK bug in your opinion? Backtrace below: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000020 0x90a594c0 in objc_msgSend () (gdb) bt #0 0x90a594c0 in objc_msgSend () #1 0x19b19130 in ?? () #2 0x9082dd0e in __CFRunLoopDoObservers () #3 0x9082cdb0 in CFRunLoopRunSpecific () #4 0x9082ca6e in CFRunLoopRunInMode () #5 0x92def878 in RunCurrentEventLoopInMode () #6 0x92deeeb9 in ReceiveNextEventCommon () #7 0x92deedd9 in BlockUntilNextEventMatchingListInMode () #8 0x93295485 in _DPSNextEvent () #9 0x93295076 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #10 0x00daadb6 in gdk_event_prepare () #11 0x02177de4 in g_main_context_prepare () #12 0x021784a6 in g_main_context_iterate () #13 0x02178bbd in g_main_loop_run () #14 0x01ca8a87 in gtk_main () #15 0x0184d888 in Gtk::Main::run () #16 0x00003ff1 in sp_main_gui () #17 0x00167234 in Inkscape::NSApplication::Application::run () #18 0x00002ef7 in main () JiHO --- http://jo.irisson.free.fr/

4 6

libgc7 issues on OS X
by MenTaLguY 03 Dec '07

03 Dec '07

By the way ... have we verified that the problematic libgc7 builds aren't being built with --enable-malloc? -mental

1 1