August 2005 - Inkscape Devel - Inkscape Mailman

Inkscape undo system
by David Yip 02 Aug '05

02 Aug '05

Can anyone point me to some code that would serve as a nice illustration of how the Inkscape undo system works? I've been reading the Session and SimpleSession classes and the way they are used in the functions in document-undo.cpp; is that a good place to begin, or are there better starting points? In particular, I'm wondering what the best way to clear the undo and redo stacks is, as it's crucial to the correct functioning of Inkboard. When a user synchronizes his or her document with another user or with a chatroom, that synchronized state must become the new original state of the user's document. sp_document_clear_undo and sp_document_clear_redo, from their code, seem to be what I want, but I can't quite figure out how to use them to attain the desired effect. -- David

2 3

[Fwd: [Linuxmovies-general] Special CinePaint Event!]
by Jon Phillips 02 Aug '05

02 Aug '05

For those attending siggraph: -------- Forwarded Message -------- > From: Robin Rowe <rower@...937...> > Reply-To: linuxmovies-general(a)lists.sourceforge.net > To: Linuxmovies-general(a)lists.sourceforge.net > Subject: [Linuxmovies-general] Special CinePaint Event! > Date: Thu, 28 Jul 2005 14:35:53 -0700 > > Special CinePaint Event! > CinePaint Birds-of-a-Feather Meeting at SIGGRAPH > Los Angeles Convention Center, Room 506 > Tuesday, August 2nd, 4pm-5pm > Open to All SIGGRAPH Attendees > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxmovies-general mailing list > Linuxmovies-general(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxmovies-general > -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

2 2

Re: [Inkscape-devel] New binary portability problem identified
by mike＠...869... 02 Aug '05

02 Aug '05

I can't tell, I only have net access at work (Windows). But a good way to check would be to run "nm inkscape | grep g_option". Alternatively, find somebody who is running a GTK+ 2.4 based system and get them to try running it. Original Message: ----------------- From: aaron@...749... Date: Mon, 01 Aug 2005 15:25:19 -0500 To: mike@...869..., inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] New binary portability problem identified Mike Hearn wrote: > Aaron, can you rebuild the autopackage against *mm 2.4 static libraries > and push a -2 release of the package, so users on GTK+ 2.4 systems can use > them again? Hey, is this one any better? I really don't know how to check. http://inkscape.modevia.com/ap/inkscape-0.42-2.x86.package Aaron Spike -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

2 1

Hi. xfig like export combined LaTeX postscript/ transparency ps export
by Marc Weber 02 Aug '05

02 Aug '05

Xfig has got one possibility to set a special flag on text which means that this text doesn't get exported on combined LaTeX ps but is written to the LaTeX file which means that you're able to also use LaTeX possibilies of typsetting mathematics and so on. Do you think it would be much effort to add this to inkscape, too? Because I *really* prefer inkscape over xfig :) inkscape could became the tool of choice making figures for LaTeX.. xfig is nice but lacks some functionality. The other thing is when exporting to ps inkscape currently just ignores transparency.. All you would have to do having two rectangles ------ -- : rect1 without ++ ---+++||| ++ : overlapping area ---+++||| || : rect2 without ++ |||||| rect2 is above rect1 would be splitting this rectangles into 3 and calculate the color of the + rectangle depending on the transparency of rect2 and color of rect1.. Then all 3 reactangles can be exported as it's done right now. And because the function Stroke to path is already provided (although I'm not sure how well it works using some advanced stroke style) it shouldn't be that hard to implement. What do you think? Marc

3 5

current CVS broken ?
by Adib Taraben 02 Aug '05

02 Aug '05

Hi, I have problem to open any dialogs besides the file-open and file-save. Inkscape closes immediately HTH, Adib. --- D:\projekte\inkscape\inkscape>gdb inkscape.exe GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: D:\projekte\inkscape\inkscape/inkscape.exe gdb: do_initial_child_stuff: process 3856 gdb: kernel event for pid=3856 tid=2772 code=CREATE_PROCESS_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_BREAKPOINT at 0x7c911230 gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 3856.0xad4 ContinueDebugEvent (cpid=3856, ctid=2772, DBG_CONTINUE); gdb: kernel event for pid=3856 tid=2772 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_ACCESS_VIOLATION at 0x004e8d99 Program received signal SIGSEGV, Segmentation fault. 0x004e8d99 in Inkscape::Verb::get_action () (gdb) bt #0 0x004e8d99 in Inkscape::Verb::get_action () #1 0x0043f8d3 in sp_ui_dialog_title_string () #2 0x005fbfc2 in sp_object_properties_dialog () #3 0x004f1f15 in sp_action_perform () #4 0x00af7a4a in g_cclosure_marshal_VOID__VOID () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #5 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #6 0x00af6cff in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #7 0x00af5434 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #8 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #9 0x015c69ff in gtk_button_clicked () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #10 0x01728c04 in gtk_toggle_button_released () #11 0x00af7a4a in g_cclosure_marshal_VOID__VOID () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #12 0x00ae370b in g_type_class_meta_marshal () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #13 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll ---Type <return> to continue, or q <return> to quit--- #14 0x00af5f6a in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #15 0x00af5434 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #16 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #17 0x015c6987 in gtk_button_released () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #18 0x015c7931 in gtk_button_button_release () from D:\projekte\inkscape\inkscape\libgtk-win32-2.0-0.dll #19 0x0168d771 in _gtk_marshal_BOOLEAN__BOXED () #20 0x00ae370b in g_type_class_meta_marshal () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #21 0x00ae34de in g_closure_invoke () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #22 0x00af6bbb in signal_emit_unlocked_R () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #23 0x00af5494 in g_signal_emit_valist () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #24 0x00af5676 in g_signal_emit () from D:\projekte\inkscape\inkscape\libgobject-2.0-0.dll #25 0x0177ab85 in gtk_widget_event_internal () #26 0x0177a7ff in gtk_widget_event () ---Type <return> to continue, or q <return> to quit--- #27 0x0168c028 in gtk_propagate_event () #28 0x0168afee in gtk_main_do_event () #29 0x0121aee9 in gdk_event_dispatch () from D:\projekte\inkscape\inkscape\libgdk-win32-2.0-0.dll #30 0x00978197 in g_main_dispatch () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #31 0x00978c90 in g_main_context_dispatch () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #32 0x00978f37 in g_main_context_iterate () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #33 0x009793da in g_main_loop_run () from D:\projekte\inkscape\inkscape\libglib-2.0-0.dll #34 0x0168a91a in gtk_main () #35 0x01ac7543 in Gtk::Main::run () at main.cc:450 #36 0x00401c97 in sp_main_gui () #37 0x0042ebf8 in Inkscape::NSApplication::Application::run () #38 0x0040165e in main () (gdb)

4 8

[Fwd: Thanks for Inkscape]
by Ted Gould 02 Aug '05

02 Aug '05

Andrew, I'm not sure on this error. I'm forwarding this message to the Inkscape development mailing list to see if someone knows there. --Ted -------- Forwarded Message -------- > From: Andrew Greig <algreig@...666...> > > Thanks for Inkscape, I have been waiting for a vector based graphics > program for quite a while, and here it is. I downloaded the Mandrake > package (urpmi inkscape) which takes care of dependencies nicely. The > program failed to start so I used a console and got this error line. > Could you advise me on how to correct this please? > > [andrew@...944... andrew]$ inkscape > inkscape: symbol lookup error: /usr/lib/libpangomm-1.4.so.1: undefined > symbol: pango_renderer_get_type > [andrew@...944... andrew]$ > > Many thanks > Andrew Greig > Melbourne, Australia

1 0

The Bag Monkey Speaks
by MenTaLguY 02 Aug '05

02 Aug '05

Here's what I've got rolled up for 0.42.1 so far: > * src/dialogs/stroke-style.cpp: backport bulia's fix for stroke width > spin button [bug number??] > > * src/text-editing.cpp: backport bulia's fix for text crash > [bug 1247066] > > * src/libnrtype/Layout-TNG-OutIter.cpp: backport cyreve fix for > crash on delete in virgin flowtext [bug 1245842] > > * configure.ac: Kees fix for libgc detection w/dlopen [bug number??] Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak. -mental

7 11

Project status Aug 1, 2005
by Bryce Harrington 02 Aug '05

02 Aug '05

The Inkscape 0.42 release garnered a huge amount of interest, and are stats are reflecting it. We rose to the 3rd most active project of the week on SourceForge today. For downloads we reached 16th, for webpage views we were 10th, for project pages we got 21st, and for tracker activity we hit 4th. Counting all hits to *.sourceforge.net we hit 6th, which was up 68 ranks since yesterday. I have a suspicion we may be going up even a bit further over the next couple days. :-) There were a number of serious bugs found post-release, especially in the packaging, so a 0.42.1 patch release will be produced hopefully some time this week, as soon as resolutions to all the issues are found. Statistics Jun 1 Jul 1 Aug 1 ========== ====== ====== ====== Max Week's Rank on SourceForge: 38 35 3 Total SF Page Views 1,935,964 3,797,037 4,452,437 Total SF Downloads 254,647 283,789 378,712 Total Freshmeat URL Hits 19,149 19,809 21,261 Total Freshmeat Subscriptions 183 189 208 Lines of Code in src/: 374,180 376,319 389,945 Code lines 260,236 261,600 270,423 Comment line 67,136 67,724 70,478 Blank 53,443 53,651 55,698 Lines of Docs in doc/: 27,790 27,792 28,090 Lines of content in website: 42,490 42,700 44,483 Size of the Inkscape wiki: 26,729 28,525 34,890 Bugs open/total: 215/1223 196/1312 215/1445 Features open/total: 453/ 728 471/ 767 440/816 Patches open/total: 11/ 230 10/ 268 8/325 CVS Commits (as per inkscape-cvs) 12,040 12,372 12,915 Inkscape-devel membership: 179 188 200 Inkscape-announce membership: 202 217 236 Inkscape-user membership: 248 258 276 Num Translations: 33 33 33 Ave Translation Ratio: 47.8 48.6 54.6

1 0

Initial commit of Inkboard code
by David Yip 02 Aug '05

02 Aug '05

Hi all, I've committed Inkboard to Inkscape CVS. This consists of the Inkboard code (in src/jabber_whiteboard), C/Gtk+ dialogs (in src/dialogs), some conversions of those dialogs to C++/Gtkmm (in ui/dialog), and modifications to some existing files. To enable Inkboard, pass the --enable-inkboard switch to the configure script. You will need libloudmouth <http://loudmouth.imendio.org> and Boost <http://www.boost.org>. I have tested Inkboard with libloudmouth v0.17.2 and v0.90, although ~v0.13 should also work. (Let me know if it really does.) I have developed this code with Boost v.1.31.0. Inkboard no longer relies on Boost smart pointers as I stated in my mailing list response to Bryce re: Summer of Code updates; I have switched all smart pointer-reliant code over to code managed by the garbage collector. However, it still uses Boost.Bind, Boost.Function, and Boost's lexical_cast. The reliance on Boost.Bind can probably be scrapped as soon as I do the work to convert the involved function objects to be used by the C++ standard library's argument-binding facilities. I think this is all the code necessary to compile Inkboard. There may be another commit coming if I forgot something, which happens more often than I'd like. If something doesn't work, please let me know. Inkboard usage ========= The "Whiteboard" toplevel menu should be present. If it isn't, try removing your menus.xml file in your Inkscape preferences directory and try again -- this will force the file to be regenerated from the built-in menu skeleton. Or, you can copy the necessary XML from src/menus-skeleton.h. You must first connect to a Jabber server; this is done by selecting Whiteboard -> Connect to server... After that, you may choose to engage in a user-to-user sharing session or a chatroom sharing session. The "Dump XML tracker" menu item is intended only for debugging; it probably should not make it into a release. Known issues ======== 1) Chatrooms must be specially created for them to work with Inkboard. Here are the conditions: A) The chatroom must broadcast the message INKBOARD-JOINED (case-sensitive) when a Jabber user enters it. This is necessary because mu-conference v0.6 doesn't seem to follow JEP-0045 with regards to the order of broadcasting presence messages. (See <http://www.jabber.org/jeps/jep-0045.html#enter-pres>.) Hopefully, this won't be a problem in the future. In the meantime, this special behavior is easy to set up with e.g. gaim. B) If regular Jabber users are present in an Inkboard chatroom before any Inkscape client joins, there will be synchronization problems, since the current Inkboard chatroom code implements the following logic: non-empty room => request synchronization. empty room => become "master". This can be worked around -- to an extent -- by checking the resource tags associated with each JID in the chatroom, since Inkboard has its own resource tag (specifically, "Inkboard"). Malicious users can, of course, defeat this, so maybe it's not the best way. We'll see. 2) Although Inkboard identifies itself as speaking the Jabber MUC protocol (which I do intend to make it do) it currently actually only acts on the "groupchat 1.0" subset of messages. 3) The bug in Ted's menus code affects Inkboard in any code path that may cause a new document window to appear. In particular, these are the cases I think are associated with said bug, based on backtraces: A) The "accept invitation in new document" option presented when a user is given the choice to accept or decline a user-to-user whiteboard session causes a crash. B) Establishing a new Inkboard session in a new document after an Inkboard session has already been established causes a crash. 4) Session files are disabled for now. They work, but only for documents that involve no references to automatically-named internal elements, which makes them a little useless. (For example, gradient/pattern fills aren't recorded correctly just yet.) If you'd like to use them, though, all the code is there. To enable them, you can (1) uncomment lines 183-184 in src/menus-skeleton.h, remove your menus.xml file, and rebuild/restart Inkscape, or (2) add in those lines to your menus.xml file. 5) Loudmouth sometimes throws errors indicating that it was asked to extract attributes or child nodes from a NULL root node. I'm not sure why it does this -- I'm pretty sure I wrapped all the code that deals with node/attribute extraction with the appropriate conditionals -- but it's possible that I've missed something. In any case, these warnings appear to be harmless -- just annoying. 6) There's quite a few g_log() debug calls still present. I apologize for this -- I think they're useful, but maybe they really aren't. I'll remove them upon request, and certainly before release. Phew. I think that's all for now. Have fun! -- David

1 0

New binary portability problem identified
by Mike Hearn 01 Aug '05

01 Aug '05

Isn't Linux fun? The problems with g_option_error_quark people are seeing is because both the static RPM and the autopackage were built against static versions of GTKmm 2.6, which introduces a silent dependency on Glib 2.6 even if only 2.4 level features are used. The solution is to build the portable binaries against *mm 2.4 static libraries. Aaron, can you rebuild the autopackage against *mm 2.4 static libraries and push a -2 release of the package, so users on GTK+ 2.4 systems can use them again? thanks -mike

4 3