- Inkscape Devel - Inkscape Mailman

RFE: [ 1469070 ] Allow dialogs to be closed by same shortcut that opened them
by Hans Nieser 13 Apr '06

13 Apr '06

Hello, I just submitted te following RFE at http://sourceforge.net/tracker/index.php?func=detail&aid=1469070&group_id=9… and was also asked to drop a note on this list, so here it is! :) > I often need to quickly adjust a grid or fill setting > (and so on) and still have my 'keyboard hand' on the > shortcut keys. What I propose is, to also allow the > dialog to be closed again by pressing the same shortcut. > > The window manager's close button can sometimes be just > a bit too small (obviously depending on which window > manager and theme one uses) for frequent use. This may > also improve workflow a bit for keyboard-lovers like me > and is hopefully trivial to implement :)

2 2

Patch: Undo History dialog
by Gustav Broberg 12 Apr '06

12 Apr '06

Hi, I have recently uploaded a patch[1] which provides an undo history dialog. It is similar to those found in e.g. GIMP[2] and Photoshop[3] (I don't know if it's in Illustrator, CorelDRAW, etc). To get an idea what it looks like without having to apply the patch, here's a screencast (in flash, sorry ;) showing it in action: http://www.csc.kth.se/~broberg/undo-history.html First of all, I'm not sure if this is a requested addition to Inkscape -- I can't recall any discussion about it on the list and I didn't find anything in the wiki. Personally, however, I do find it useful (at least occasionally), so I went ahead and implemented it. Secondly (if it's found to be of value), this patch could use some rather heavy reviewing. It's my first patch and I'm not confident enough with the code base to feel sure about what the "right" solutions are. Here are some additional concerns: * To get the type of an event I rely entirely on the current event context. This obviously not (always) a correct assumption. An example of this problem: setting an object's color while the node tool is the current context. * In order to populate the tree with icons I added a help function to widget/icon.cpp to get the internal Pixbuf of an icon. This could be solved in much a better way when the gktmmified stock icon system is in place, but for now, this was easiest way for me to solve it. * There are bugs lurking which I have not been able to reproduce. Some seem to be the result of problems with undoing of certain types of events; i.e. the bugs are in the current code. I'm looking into this... For now, here is at least one I managed to nail down and put in the tracker: http://sourceforge.net/tracker/index.php?func=detail&aid=1423038&group_id=9… 1. http://sourceforge.net/tracker/index.php?func=detail&aid=1423034&group_id=9…) 2. http://docs.gimp.org/images/dialogs/dialogs-undo-history.png 3. http://homepage.cs.uri.edu/tutorials/PhotoshopEl/Help/images/wa_11.gif -- Gustav Broberg

6 9

DOM update
by Bob Jamison 12 Apr '06

12 Apr '06

Hi, all, This morning we updated the /dom directory. Basically we ripped up the old one, and added a new one. So there will be a large svn update tonight. We worked toward making sure that the build is not broken, but there might be minor details on Linux or OSX. Please let me know if there are any problems. This was necessary to move forward with .odg output, which should start taking shape soon. Considerable thanks to Aaron and Cornelius for helping me with this. bob

2 1

[Fwd: Vektorgrafik-Test in der c't]
by Adib Taraben 12 Apr '06

12 Apr '06

Hello all, I got a message from Peter Koenig an writer for the german computer mag C't. C't is a 2 weekly high level computer mag. They are doing a comparison of free and cheap (does not cost much) vector-graphics-software. So they are also dealing with Inkscape. The article will be published on May 15th. They give all originators the possibility to review the test-results. The results will be delivered until April 18th and they need feedback until April 27th. As the time-frame is tight the writer ask for point of contact for the test-results and upcoming technical questions. Me: As the paper is in german I will ask him to write the results to me and Colin (another german). I think the results should not go to the wild before issuing the mag on the kiosk. Technical issues should go to inkscape-devel. So stay tuned, Adib. -------- Original Message -------- Subject: Vektorgrafik-Test in der c't Date: Wed, 12 Apr 2006 11:12:02 +0200 From: Peter König <pek@...883...> To: Adib Taraben <taraben.a@...50...> Hallo, voraussichtlich in c't-Ausgabe 11/2005 (Erstverkaufstag am 15. Mai) wird ein Test preiswerter und kostenloser Vektorgrafik-Software erscheinen, wobei Inkscape im Testfeld vertreten sein wird. Wir möchten allen Herstellern Gelegenheit geben, die Abschnitte und Tabelleneinträge, die ihr Produkt betreffen, vor Drucklegung zu prüfen. Diese Auszüge aus dem Testbericht verschicken wir per E-Mail, voraussichtlich bis zum 18. April. Ihr Feedback sollte uns bis spätestens 27. April erreicht haben. Da dieser Zeitplan einigermaßen eng ist, würde ich gerne wissen, ob ich mit dieser Anfrage bei Ihnen an der richtigen Adresse bin und wer sich genau bei Ihnen mit dieser Angelegenheit befassen wird. An wen soll ich die Auszüge aus dem Testbericht schicken und wer kann während des Test eventuell auftauchende technische Fragen beantworten? Vielen Dank und mit freundlichen Grüßen, Peter König c't - Magazin für Computertechnik http://www.heise.de/ct/ Heise Zeitschriften Verlag GmbH & Co.KG phone: 0511-5352-763 Helstorfer Str. 7 fax: 0511-5352-417 D-30625 Hannover, Germany eMail: pek@...883...

1 0

WEBFORM for an update
by marcus y 12 Apr '06

12 Apr '06

Message from Inkscape submission form Please note, that the submitter may not read this list. CC your answer to the submitter name: marcus y email: marcus-yass@...1231... submitted the following: Just a sujustion in case you release an update to inkscape. Perhaps you should treat gradient lines more like objects(allow for grouping to the objects they are aplied to). Also, if you can, have the four corners of an imported bitmap treated as nodes, to allow for perspective style deforming. Oh, the pattern converter doesn\'t seem to have much use, the way the program illistrates the spaces beetween objects that are exactly \"touching\" is intrusive, there\'s no way to get around it so it needs fixing. Thanks (that is, if you listen)

1 0

inkscape build report
by Bryce Harrington 10 Apr '06

10 Apr '06

Some new warnings in dom/ziptool.cpp. ----- Forwarded message from root <root@...1070...> ----- Date: Mon, 10 Apr 2006 05:21:15 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Mon Apr 10 05:20:20 2006 (Run 2020) Snapshot: inkscape-20060410-0400.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 16 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == sp-flowtext.cpp:339: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:744: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:733) sp-shape.cpp:609: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:486: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:650: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:729: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) dom/ziptool.cpp:1531: warning: comparison between signed and unsigned integer expressions dom/ziptool.cpp:1654: warning: unused variable `int cm' dom/ziptool.cpp:1659: warning: unused variable `bool ftext' dom/ziptool.cpp:1672: warning: unused variable `time_t mtime' dom/ziptool.cpp:1677: warning: unused variable `int xfl' dom/ziptool.cpp:1682: warning: unused variable `int os' == Environment Summary == ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

Icons.... ?
by Jon A. Cruz 09 Apr '06

09 Apr '06

So... Who cares about icons? Themes, styles, names, fallbacks, matching FDO and CREATE and Tango!, etc... In squashing the Evil Giant Eyeball (which mutated from the horrid large eyeball), I've landed square in the middle of icon code again, so was wondering if anyone has things to be addressed while I'm in there. references: http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec- latest.html http://tango-project.org/Tango_Desktop_Project http://tango-project.org/Standard_Icon_Naming_Specification Supplemental: http://tango-project.org/ArtLibreSet

5 7

presentation functionality
by Rick 08 Apr '06

08 Apr '06

This is a probe to see if there is any thought being given towards automation of presentation (a la powerpoint) functionality in InkScape. A a whole lot can be done now for static presentations. But some simple scripting features would be really useful. For instance: I like to add popup text boxes which can be handled by adding simple mouseover/mouseout calls to toggle visibility on a caption. This works in FireFox, (although it would be 'really' nice if SVG fonts worked too) I imagine that this would be ways down the road, and probably fairly complicated to integrate, but is there a plan for this type of functionality? -- Cheers! Rick

2 1

Translatable SVG document support
by Andrius Ramanauskas 08 Apr '06

08 Apr '06

Hi, I am currently planning to add support for internationalized (translatable) SVG documents. And I guess it is better to share my thoughts before going deep to implementation, so everyone will be aware of my plans and maybe someone will criticize or adjust my plans. My current plan is to implement this in steps: * 1 step - <switch> support. I already tested prototype of semi-working switch element support, but there still some work to do. Currently switch element works just like <g>, but I will make it work according to SVG standard - to render only first element which conditional properties evaluate to true (I will implement support for "systemLanguage" property for a start, which will evaluate to true if property is not set or contains current document language). I plan to make SPSwitch a subclass of SPGroup, so user can enter switch element (turn it into a temporery layer, which will show all contained items, not just first) * 2 step - bitmap export by language (ability to define language to use for <switch> in command line) * 3 step - export/import of texts. Import will also create <switch> elements if not already created * 4 step - UI support for language. I don't know for sure how it should be implemented, but I guess there should be a menu item to turn text to switch ("Make translatable") and language combo in Text dialog (to be shown only if switch is selected) Anyway, I'm open for there are any suggestions or objections. Andrius

3 3

Markup in verbs.cpp
by Jon A. Cruz 08 Apr '06

08 Apr '06

I just noticed a problem in verbs.cpp The tooltips in the toolbar show raw escapes instead of the character being represented. That is... I see "Rotate selection 90° clockwise" instead of "Rotate selection 90º clockwise" I noticed that one went in on a checkin for fixing things inside of menus. That seems to work for me. However, it appears to be at the expense of the tooltips. Since GTK+ is all UTF-8 based, I tried changing it to escaped literal UTF-8 values. "Rotate selection 90\xC2\xB0 clockwise" now makes it work in both locations for me. Sooooo..... does anyone else see the problem? And/or does anyone know of a better correction for it?

1 0

Announcing InkscapeSVG
by unknown＠example.com 07 Apr '06

07 Apr '06

Greetings fellow Inkscapers, This announcement is a couple of days late due to problems establishing our new project web site.... but as the say, better late than never. Much hard work has gone into developing Inkscape, the world's best free vector drawing program. But times are a-changing. The world is being Googled. Applications must be web based. We, who firmly believe in the open SVG standard, must move on too. Thus it gives us great pleasure to announce that our future efforts will be towards creating InkscapeSVG, a web based vector drawing program written in... ta-daa... SVG itself! Already a prototype exists including several basic shape tools and a swatches pallete. You can check out development at: http://inkscapesvg.free.fr Make sure you check out the nifty text tool too! Sincerely, Your InkscapeSVG team.

5 7

Large checkin for sizes
by Jon A. Cruz 07 Apr '06

07 Apr '06

I just did a checkin of 22 files to start cleaning up the icon size issue. Although there were many files touched, the actual line count is fairly low. The main thing is to switch off of use of the GtkIconSize enum. For end programmers out there, the change is only from "GtkIconSize" to "Inkscape::IconSize" and from "GTK_ICON_SIZE..." to "Inkscape::ICON_SIZE...". Thus it should be a very low-impact one. So please give things the once-over to make sure nothing snuck in as far as side-effects go (it did pass 'make check' and all the other smoke tests I ran, but it's always good to check). The thing this checkin should have achieved is isolating use of GtkIconSize to just two main files. That way the work to change some icons smaller can go in easily. For those who care about details... The calls for themeable stock items use GtkIconSize as a base, but then allow for arbitrary string-based sizes to be registered for new int values. Thus we can't simply extend their enum with +1 and use that directly. Instead we need to add in a lookup to translate at run- time from our extended enum to the types registered dynamically. This buys us quite a lot of functionality, and only needs extra work in a single file. First phase was to encapsulate the use of GtkIconSize in those two main locations. The second phase is to add the dynamic mapping of enum/int values. Then the third stage will be to change selected things (like the eye and the lock) to use Inkscape::ICON_SIZE_DECORATION.

1 1

Windows XP: Interface very slow
by Michael Gorbach 07 Apr '06

07 Apr '06

I am trying to use inkscape on winxp pro sp2 and the program does not run well at all. The drawing of widgets by gtk is very slow. I can see black rectangles appearing where the menu should be before the menu is drawn. Is this a known issue of some kind? Is there a fix? Michael Gorbach

4 5

Do a CVS visualization study, GET CASH
by Eric Gilbert 07 Apr '06

07 Apr '06

Hi, I am a graduate student at the University of Illinois at Urbana- Champaign. I am doing a study soon on the effects of CVS and mail visualization on open source communities. Check out my work here: http://social.cs.uiuc.edu/people/gilbert/research.html (info on the projects) http://social.cs.uiuc.edu/people/gilbert (info on me) If you are a developer, I could use your help. Look at the visualization, do some surveys and we give you a $20 gift certificate to newegg.com. I am not ready quite yet; still waiting on IRB approval (http:// www.irb.uiuc.edu/). Please keep us in mind if you are interested... I will ask again soon, and then that's all the spam. Contact me if you want more information now. Thanks, Eric -- "Tyranny is tyranny, let it come from whom it may." -- Revolutionary conscripts, 1776

1 0

svn 11251 dumps core
by inkbottle 07 Apr '06

07 Apr '06

Here is a reproducible crash on svn revision 11251. My 12-year old found this crash running .43 on FC4. I reproduced the problem on FC5 at the tip of svn, rebuilt inkscape debug and produced a stack trace from the core file. The crash is caused reliably in the following way. Enter some text. Zoom in on the text, or make it big enough to work with easily. The text I used was "This is some text". Select the text tool. use that tool to select,say, the initial T. Change the size of the text to something else noticeably different, it doesn't matter what. The T changes size appropriately. Then place a gradient on the text string as a whole. Now select, say, the s in 'some' with the text tool. Change the size of that s to any other size. Poof! inkscape dumps core, and vanishes. Here is the gdb backtrace. It is a bit beyond me at the moment. This has something to do with text, gradients and, from the backtrace, selection and styles. I'm hoping someone can make more sense of the backtrace than I. (gdb) where #0 0x005ec402 in __kernel_vsyscall () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #1 0x00e22159 in raise () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #2 0x00e236e3 in abort () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #3 0x082d1ca8 in inkscape_segv_handler (signum=11) at inkscape.cpp:375 #4 <signal handler called> #5 0x08648c53 in Inkscape::UI::Widget::SelectedStyle::update (this=0xa74e800) at ui/widget/selected-style.cpp:893 #6 0x086495e1 in ss_selection_changed (data=0xa74e800) at ui/widget/selected-style.cpp:46 #7 0x08649618 in ss_selection_modified (selection=0xa6affc0, flags=11, data=0xa74e800) at ui/widget/selected-style.cpp:52 #8 0x0838d6da in sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>::operator() (this=0xa7a6110, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4, _A_a3=@0xbfa52af4) at /usr/include/sigc++-2.0/sigc++/functors/ptr_fun.h:185 #9 0x08662e17 in sigc::adaptor_functor<sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void> >::operator()<Inkscape::Selection* const&, unsigned int const&, Inkscape::UI::Widget::SelectedStyle*&> (this=0xa7a610c, _A_arg1=@0xbfa52be4, _A_arg2=@0xbfa52bf4, _A_arg3=@0xa7a6114) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:123 #10 0x08662e4e in sigc::bind_functor<-1, sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>::operator()<Inkscape::Selection* const&, unsigned int const&> (this=0xa7a6108, _A_arg1=@0xbfa52be4, _A_arg2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/adaptors/bind.h:1144 #11 0x08662e78 in sigc::internal::slot_call2<sigc::bind_functor<-1, sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void, Inkscape::Selection*, unsigned int>::call_it (rep=0xa7a60f0, a_1=@0xbfa52be4, a_2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:173 #12 0x082e7d19 in sigc::internal::signal_emit2<void, Inkscape::Selection*, unsigned int, sigc::nil>::emit (impl=0xa7a3ca8, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/signal.h:832 #13 0x082e7de2 in sigc::signal2<void, Inkscape::Selection*, unsigned int, sigc::nil>::emit (this=0xa6afff0, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/signal.h:1924 #14 0x082e661a in Inkscape::Selection::_emitModified (this=0xa6affc0, flags=11) at selection.cpp:93 #15 0x082e6651 in Inkscape::Selection::_emit_modified (selection=0xa6affc0) at selection.cpp:85 ---Type <return> to continue, or q <return> to quit--- #16 0x00d8b6e1 in g_list_remove_link () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #17 0x00d8d09d in g_main_context_dispatch () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #18 0x00d9032f in g_main_context_check () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #19 0x00d906d9 in g_main_loop_run () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #20 0x03b39a6b in gtk_dialog_run () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #21 0x082d25ef in inkscape_segv_handler (signum=11) at inkscape.cpp:525 #22 <signal handler called> #23 0x08648c53 in Inkscape::UI::Widget::SelectedStyle::update (this=0xa74e800) at ui/widget/selected-style.cpp:893 #24 0x086495e1 in ss_selection_changed (data=0xa74e800) at ui/widget/selected-style.cpp:46 #25 0x086495fd in ss_subselection_changed (dragger=0xa659a00, data=0xa74e800) at ui/widget/selected-style.cpp:58 #26 0x084f9f96 in sigc::pointer_functor2<void*, void*, void>::operator() ( this=0xa7a61a8, _A_a1=@0xbfa538c4, _A_a2=@0xbfa53804) at /usr/include/sigc++-2.0/sigc++/functors/ptr_fun.h:147 #27 0x08662ea4 in sigc::adaptor_functor<sigc::pointer_functor2<void*, void*, void> >::operator()<void* const&, Inkscape::UI::Widget::SelectedStyle*&> ( this=0xa7a61a4, _A_arg1=@0xbfa538c4, _A_arg2=@0xa7a61ac) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:103 #28 0x08662ed3 in sigc::bind_functor<-1, sigc::pointer_functor2<void*, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>::operator()<void* const&> (this=0xa7a61a0, _A_arg1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/adaptors/bind.h:1122 #29 0x08662ef7 in sigc::internal::slot_call1<sigc::bind_functor<-1, sigc::pointer_functor2<void*, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void, void*>::call_it (rep=0xa7a6188, a_1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:137 #30 0x0837e5ae in sigc::internal::signal_emit1<void, void*, sigc::nil>::emit ( impl=0xa7a6158, _A_a1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/signal.h:686 #31 0x0837e66f in sigc::signal1<void, void*, sigc::nil>::emit (this=0xa6aef94, _A_a1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/signal.h:1812 #32 0x08377605 in SPDesktop::emitToolSubselectionChanged (this=0xa6aee00, data=0xa659a00) at desktop.cpp:1017 ......

3 2

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 07 Apr '06

07 Apr '06

Bunch of new warnings today in knot.cpp. Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Thu, 06 Apr 2006 17:21:33 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Thu Apr 6 17:10:56 2006 (Run 1936) Snapshot: inkscape-20060406-1600.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 27 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == knot.cpp:109: warning: invalid access to non-static data member `SPKnotClass::event' of NULL object knot.cpp:109: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:118: warning: invalid access to non-static data member `SPKnotClass::clicked' of NULL object knot.cpp:118: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:127: warning: invalid access to non-static data member `SPKnotClass::doubleclicked' of NULL object knot.cpp:127: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:136: warning: invalid access to non-static data member `SPKnotClass::grabbed' of NULL object knot.cpp:136: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:145: warning: invalid access to non-static data member `SPKnotClass::ungrabbed' of NULL object knot.cpp:145: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:154: warning: invalid access to non-static data member `SPKnotClass::moved' of NULL object knot.cpp:154: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:163: warning: invalid access to non-static data member `SPKnotClass::request' of NULL object knot.cpp:163: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:172: warning: invalid access to non-static data member `SPKnotClass::distance' of NULL object knot.cpp:172: warning: (perhaps the `offsetof' macro was used incorrectly) sp-flowtext.cpp:339: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:744: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:733) sp-shape.cpp:609: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:644: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:723: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) trace/trace.cpp:196: warning: unused variable `Inkscape::XML::Node*imgRepr' == Environment Summary == ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

Clipping and masking bugs
by Tavmjong Bah 06 Apr '06

06 Apr '06

Hi, I've begun to update my book for 0.44. Should be a great release! But, I have run into a few bugs with a version of Inkscape from SVN a day or two ago. The following file can be used to illustrate the problems: http://tavmjong.free.fr/INKSCAPE/DRAWINGS/ClipMask2.svg The raw objects for clipping and masking are on the left, the clipped and masked objects (blue rectangles) are on the right. In the case of the first two items, the file is displayed correctly in Firefox trunk. 1. Clipping using stroked text without fill doesn't seem to work. 2. The masked object is invisible when the file is saved and reopened. The masked object can be restored by selecting the object, unmasking and remasking. 3. Sometimes the display of the gradient is not updated when the gradient tool is used to adjust it. Try editing the gradient in the above document by dragging a gradient node. 4. Not really a bug... but very confusing. The gradient editor does not switch to the gradient selected with the the gradient tool. This behavior is different from all other dialogs. If needed, I'll file bug reports but I thought I would bring them up here first. Tav

2 3

IO::Resource vs. Binreloc
by Aaron Spike 06 Apr '06

06 Apr '06

I was going to build an autopackage this morning for those who would like to play with the new keymaps but the build errored out with the following message. I'm assuming that it is caused by Binreloc because that is something that is different in the autopackage build. I understand some of the words but it is still a little beyond me. mental? Aaron Spike io/resource.cpp: In function ‘Inkscape::Util::ptr_shared<char> Inkscape::IO::Resource::get_path(Inkscape::IO::Resource::Domain, Inkscape::IO::Resource::Type, const char*)’: io/resource.cpp:38: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:39: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:40: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:41: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:42: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:43: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:44: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:45: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:46: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:47: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:48: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:49: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:50: error: invalid conversion from ‘const char*’ to ‘gchar*’

2 2

[new] configurable keymaps
by MenTaLguY 06 Apr '06

06 Apr '06

I've just committed basic support for configurable keymaps. You'll probably need to do a fresh ./configure to get share/keys -- and a 'make install' to install share/keys/default.xml and get your keyboard shortcuts back! share/keys/default.xml contains the default key configuration for Inkscape; until I document the format further, you can use it for reference when developing your own keymaps. The key names in it are GDK keysym names. share/keys/default.xml gets loaded first, followed by ~/.inkscape/keys/default.xml if it exists. At present, a user keymap is overlaid on the system keymap rather than clearing it completely. -mental

1 0

Icons, and cursors, and multiples... oh my
by Jon A. Cruz 05 Apr '06

05 Apr '06

I was skimming through my log, and noticed a few things that could be brought up here... First is reusing the icon code for cursors. This is probably a good idea, and for even more reason than thought. One of the additional benefits would be nice fallback to CREATE assets, etc. I'm fairly up on the various bits of code involved, and also cursor stuff, so definitely hit me up about it. Oh... and a minor point... the XPM spec (what we use for our cursors currently) allows for the hot X and Y to be in the XPM file itself. I was looking at this a bit, as it would take the position hardcoding out of our source code that loads icons. The default routines don't give you X and Y, but I can add it easily. We probably could fold this in to the other cursor work with minimal effort. Then there's the whole thing about multiple export. It's actually not to hard to do... and something I'm doing in the Icon Preview dialog. With just a little bit of tuning, that can be refactored to also support multiple-res export. This would be good for icons and cursors, and is very low-hanging fruit in that I can probably get it going in a day or so. Plus there've been enough user requests to make something like that worthwhile. So... start thinking about how this could be done for the most effect with the least effort. Hitting cursors and icon needs would be the minimum. Roughing this out could help both the export and the preview. Oh, and one of the other features I was looking at was adding librsvg rendering to the icon preview window. Again, I've done all the research on it and it will take only a small bit of coding (perhaps less than hooking in LittleCms took). I'm wondering if this might be useful as an option for the multi-export, in addition to the preview window. Anyway, start thinking about all this. There's a lot we can do to combine a few simple things and end up with some powerful workflow tools. UI, command-line invocation and use cases of different types of users could all be helpful.

1 0

printing
by Mickael Drean 05 Apr '06

05 Apr '06

Hi there, Recently i started to develop with Gtkmm and I need to print and export custom Widget to picture file. As Inkscape is capable of doing it, i 'd like to know how you dit it. Do you use an external librairy? or have you developped the functionnality? Please, could you help me to achieve my goals? Thanks, Mick PS: my english may be unclear, do not hesitate to say it...

2 1

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 05 Apr '06

05 Apr '06

Build system is picking up an error in svg-color-test.h... Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Tue, 04 Apr 2006 17:21:16 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Tue Apr 4 16:54:55 2006 (Run 1886) Snapshot: inkscape-20060404-1400.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 12 2 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == svg/svg-color-test.h:26: error: `assert' undeclared (first use this function) svg/svg-color-test.h:26: error: (Each undeclared identifier is reported only once for each function it appears in.) == Warnings == sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-image.cpp:516:8: warning: extra tokens at end of #endif directive sp-item.cpp:730: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:719) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:644: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:723: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) trace/trace.cpp:196: warning: unused variable `Inkscape::XML::Node*imgRepr' == Environment Summary == ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

[Portland] File dialog as trusted desktop service
by Bryce Harrington 05 Apr '06

05 Apr '06

----- Forwarded message from "Bastian, Waldo" <waldo.bastian@...1100...> ----- Date: Mon, 20 Mar 2006 08:26:45 -0800 From: "Bastian, Waldo" <waldo.bastian@...1100...> To: portland@...626... Subject: [Portland] File dialog as trusted desktop service FYI Waldo Bastian Linux Client Architect - Channel Platform Solutions Group Intel Corporation - http://www.intel.com/go/linux OSDL DTL Tech Board Chairman -----Original Message----- From: gtk-devel-list-bounces@...45... [mailto:gtk-devel-list-bounces@...45...] On Behalf Of Mark Seaborn Sent: Saturday, March 18, 2006 9:22 AM To: gtk-devel-list@...45...; gtk-list@...45... Subject: ANNOUNCE: Plash 1.16, with Powerbox for Gtk Hi folks, I have released a new version of Plash, which is available from: http://plash.beasts.org Plash is a system for sandboxing GNU/Linux programs so that they can be run with minimum authority/privileges. Plash can be used with GUI applications: you can dynamically grant a GUI application access rights to individual files that you want to open and edit. This happens transparently through the Open/Save file chooser dialog box. Plash replaces Gtk's GtkFileChooserDialog so that the file chooser is implemented outside the application in a separate process, as a trusted component. This file chooser is known as a powerbox, because it delegates additional power to the application. For example, Inkscape can be launched in a sandbox using the following command. Initially it won't have access to anything in your home directory. Choosing a file using File->Open grants Inkscape access to the file, attaching the file into Inkscape's file namespace. pola-run --prog /usr/bin/inkscape \ -B -fl /etc --x11 \ --env LD_PRELOAD=/usr/lib/plash/lib/powerbox-for-gtk.so \ --powerbox --pet-name "Inkscape" The main change in this release is a reimplementation of the powerbox/Gtk integration. In the previous version, the replacement GtkFileChooserDialog class inherited only from GtkObject, which caused various problems. The new version inherits from GtkDialog (and hence from GtkWindow, GtkWidget, etc.), just as the ordinary GtkFileChooserDialog does. This works with a lot more Gtk applications. The new GtkFileChooserDialog replacement prevents its parent GtkWindow from opening a window by overriding the GtkWidget "map" method with code that does not pass the call on to GtkWindow. Instead, the "map" method invokes the powerbox API, which causes the powerbox manager to open a file chooser instead. You can see the code for this at: new: http://svn.gna.org/viewcvs/plash/trunk/src/gtk-powerbox.c old: http://svn.gna.org/viewcvs/plash/trunk/src/gtk-powerbox-noninherit.c This still works as an LD_PRELOADed library, which replaces gtk_file_chooser_* functions. Would there be any interest in merging this functionality into mainline Gtk, so that the powerbox code can optionally be compiled in, and optionally be enabled at run time? Mark _______________________________________________ gtk-devel-list mailing list gtk-devel-list@...45... http://mail.gnome.org/mailman/listinfo/gtk-devel-list _______________________________________________ Portland mailing list Portland@...626... http://lists.freedesktop.org/mailman/listinfo/portland ----- End forwarded message -----

1 0

next about screen
by Jon Phillips 04 Apr '06

04 Apr '06

Who is doing the next about screen? It seems like it should be added in here soon...is there a time-table for this? Jon -- 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) Creative Commons (www.creativecommons.org) San Francisco Art Institute (www.sfai.edu)

5 7

WEBFORM TurboMilk Blog
by Dmitri Joukov 04 Apr '06

04 Apr '06

Message from Inkscape submission form Please note, that the submitter may not read this list. CC your answer to the submitter name: Dmitri Joukov email: dmitri@...1228... submitted the following: We wrote about Inkscape in our blog. Please check it out http://blog.turbomilk.com/archives/000058.html. Thanks for attention! -- Dmitri Joukov

2 1