August 2007 - Inkscape Devel - Inkscape Mailman

Windows console
by Gail Banaszkiewicz 21 Aug '07

21 Aug '07

I seem to have lost the ability to run Inkscape as a console app in Windows. I have followed the instructions in http://wiki.inkscape.org/wiki/index.php/FAQ#Can_Inkscape_be_used_from_the_c… so is it possible that something has changed in the last while during the broken build period? Is anyone else on Windows having the same problem or is it just me (and therefore likely my own error)? Thanks! Gail

3 3

SoC: Font Specification Implementation
by Gail Banaszkiewicz 20 Aug '07

20 Aug '07

Hi all! I uploaded a patch into the patch tracker with my work from the second half of Summer of Code: Patch #1778026 <https://sourceforge.net/tracker/index.php?func=detail&aid=1778026&group_id=…>. I did this instead of checking it in because although I have done a lot of testing, I think it would be prudent if you all give it a try as well. It should be non-obtrusive for you to try; the only real visual difference should be that the text and style dialog shows only those fonts that Pango can actually work with (so no more duplicates, and no more styles that aren't selectable). Everything else is under the hood so to speak. This work allows for us to separate font families and styles better in the text and style dialog. I held off implementing this for now as Miklos has some code he thinks will work well for this purpose in svgbuilder.cpp. I was hoping we could all have a look at his code and decide whether that's what we want to use for this purpose. I also wanted to make sure the framework I laid down for this is solid before going on to the next stage. I have also laid the foundation for being able to support fonts that CSS can't. At the moment this isn't possible given the fact that Pango only supports CSS fonts. However, I will be doing some more research in the near future into either getting that changed, or seeing if there is any way around using the PangoFontDescription structure that we rely on so heavily at the moment (which is the one that specifically does not support anything outside of CSS). Please let me know if you find any issues or annoyances! I am getting married this week, have a week off next week, and am travelling the week after. So communication could be sporadic - but don't worry, I have not abandoned you! ;) Gail

1 0

.SVG filetype
by Thomas Worthington 20 Aug '07

20 Aug '07

I get EPS files from clients every week with existing logos and other design elements from their letterhead and other advertising in them. Problem is, most of these files are little more than wrappers around Illustrator-only code and can not be displayed by anything other than Adobe products, certainly Inkscape can handle maybe 1 in 10 of them and even then very poorly. This is not Inkscape's fault but the fault of products that save files in "<product>-eps" format. The practical upshot for me is that ".eps" is now a meaningless filetype, much like .tiff, and serves only to make it difficult to explain to clients why I'm having trouble with what they think of as very basic files. As this problem has grown, I've started to question the value of having "Save as inkscape SVG" produce ".svg" suffixed files. Is it not a better idea, design-wise, to indicate that a file is not "pure" SVG with a different suffix such as .isvg or something similar? I have already sent Inkscape-SVG files to other designers by mistake; with a different suffix this would be a mistake which would be apparent as I selected the files for attachment to my emails. Should Inkscape change the default suffix for its own filetypes? Thomas Worthington

7 8

Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] inkscape/trunk/src/ui/dialog
by joel＠...1709... 20 Aug '07

20 Aug '07

Oh good work; well done! ---------------------------------------- From: "Bruno Dilly" <bruno.dilly@...400...> Sent: 20 August 2007 05:15 To: joel@...1709... Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] inkscape/trunk/src/ui/dialog Hey Joel, I made the changes you've suggested. Thanks by the support. On 8/19/07, joel@...1709... wrote: > Great, and I just noticed one other thing. > > In ocaldialogs.h you have the line > FileDialogOCALBase(const Glib::ustring &title) : > Gtk::Dialog(title,true) > > where you call the constructor of Gtk::Dialog. Can you use instead the three > parameter > version where the parent window is specified as the second parameter? Like > this... > > FileDialogOCALBase(const Glib::ustring &title, Gtk::Window& parent) : > Gtk::Dialog(title, parent, true) > > This should be pretty easy considering the OCAL classes already get a > reference > to the parent window from file.cpp. The advantage of doing this for Windows > users, is > that it stops your dialogs sinking down behind the inkscape desktop if > someone clicks > on it. > > Best regards > Joel > > ________________________________ > From: "Bruno Dilly" > Sent: 19 August 2007 10:54 > To: joel@...1709... > Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] > inkscape/trunk/src/ui/dialog > > OK Joel, I will do it soon. Thanks for the help =) > > On 8/19/07, joel@...1709... wrote: > > I figured out what the problem was now. In my version, I made changes in > > file.cpp, which I managed to miss comitting. I'm very sorry for all the > > inconvenience. I assumed you were asleep, and I was hoping to slip the > > change in quickly before you woke up - well that worked out just great! > > > > On the subject of file.cpp, the line in the current SVN version > > exportDialogInstance = > > Inkscape::UI::Dialog::FileExportToOCALDialog::create( > > was > > exportDialogInstance = new > > Inkscape::UI::Dialog::FileExportToOCALDialog( > > in my version. > > > > Can I suggest that you do the same, when you're ready? There's no need to > > have separate dialog and impl classes in this case. If possible I suggest > > you begin to merge the functionality of the two classes, do away with the > > class factory, and just expose the constructor directly. This sounds like > a > > big deal, but actually it only took me about 10 minutes to do. > > > > Hope that helps > > > > Best Regards > > Joel > > > > ________________________________ > > From: "Bruno Dilly" > > Sent: Sunday, August 19, 2007 10:09 AM > > To: joel@...1709... > > Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] > > inkscape/trunk/src/ui/dialog > > > > But I think I didn't erased any modification. > > > > I just included in the file.cpp you have commited the following itens: > > - an #include "ui/dialog/ocaldialogs.h" > > - the password verification inside the export to ocal function > > > > But if you think is necessary to revert, do it, and I will fix it > > later, if necessary. > > > > On 8/19/07, joel@...1709... wrote: > > > Well it's good that you fixed it. I'm confused though, because I tested > > and > > > compiled my revised version *several* times. Did you guys try running > > > ./autogen ? Now file.cpp needs to be reverted, as my version did away > with > > > the class factories. > > > > > > ________________________________ > > > From: Jon Phillips > > > Sent: Sunday, August 19, 2007 6:30 AM > > > To: Bruno Dilly > > > Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: > [15827] > > > inkscape/trunk/src/ui/dialog > > > > > > On Sun, 2007-08-19 at 02:11 -0300, Bruno Dilly wrote: > > > > I was doing the same thing as Joel, and I was including the login > > > > dialog used to export to ocal. > > > > > > > > So I commited my ocaldialogs.ccp and ocaldialogs.h, and now things > look > > > fine. > > > > > > Whoa, you guys gotta inter-communi-kate ;) > > > > > > Jon > > > > > > > On 8/19/07, MenTaLguY wrote: > > > > > Joel, your recent commit appears to have broken the build. > > > > > > > > > > Please fix it so we can get back to work. > > > > > > > > > > Thanks, > > > > > > > > > > -mental > > > > > > > > > > On Sat, 2007-08-18 at 17:29 -0700, > > > joelholdsworth@...58... > > > > > wrote: > > > > > > Revision: 15827 > > > > > > > > > > > > http://inkscape.svn.sourceforge.net/inkscape/?rev=15827&view=rev > > > > > > Author: joelholdsworth > > > > > > Date: 2007-08-18 17:29:36 -0700 (Sat, 18 Aug 2007) > > > > > > > > > > > > Log Message: > > > > > > ----------- > > > > > > Separated the OCAL import and export dialogs into their own source > > > file - ocaldialogs.cpp and ocaldialogs.h > > > > > > > > > > > > Modified Paths: > > > > > > -------------- > > > > > > inkscape/trunk/src/ui/dialog/Makefile_insert > > > > > > inkscape/trunk/src/ui/dialog/filedialog.cpp > > > > > > inkscape/trunk/src/ui/dialog/filedialog.h > > > > > > > > inkscape/trunk/src/ui/dialog/filedialogimpl-gtkmm.cpp > > > > > > > inkscape/trunk/src/ui/dialog/filedialogimpl-gtkmm.h > > > > > > > > > > > > Added Paths: > > > > > > ----------- > > > > > > inkscape/trunk/src/ui/dialog/ocaldialogs.cpp > > > > > > inkscape/trunk/src/ui/dialog/ocaldialogs.h > > > > > > > > > > > > > > > > > > This was sent by the SourceForge.net collaborative development > > > platform, the world's largest Open Source development site. > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > > This SF.net email is sponsored by: Splunk Inc. > > > > > > Still grepping through log files to find problems? Stop. > > > > > > Now Search log events and configuration files using AJAX and a > > > browser. > > > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > > _______________________________________________ > > > > > > Inkscape-cvs mailing list > > > > > > Inkscape-cvs(a)lists.sourceforge.net > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-cvs > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > This SF.net email is sponsored by: Splunk Inc. > > > > > Still grepping through log files to find problems? Stop. > > > > > Now Search log events and configuration files using AJAX and a > > browser. > > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > _______________________________________________ > > > > > Inkscape-devel mailing list > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > > > Still grepping through log files to find problems? Stop. > > > > Now Search log events and configuration files using AJAX and a > browser. > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > _______________________________________________ > > > > Inkscape-devel mailing list > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > -- > > > 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... > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > Inkscape-devel mailing list > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > Inkscape-devel mailing list > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > >

1 0

win32 building again
by Bob Jamison 20 Aug '07

20 Aug '07

Well, finally, we got Inkscape to build again. It is here: http://inkscape.modevia.com/win32/Inkscape0708190932.7z It is built with the new library bundle: http://inkscape.modevia.com/win32libs/gtk210-070819.7z The build.xml file has been tweaked to use this. You no longer need the separate boost installation. bob frabjous day!

3 6

Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] inkscape/trunk/src/ui/dialog
by joel＠...1709... 20 Aug '07

20 Aug '07

Great, and I just noticed one other thing. In ocaldialogs.h you have the line FileDialogOCALBase(const Glib::ustring &title) : Gtk::Dialog(title,true) where you call the constructor of Gtk::Dialog. Can you use instead the three parameter version where the parent window is specified as the second parameter? Like this... FileDialogOCALBase(const Glib::ustring &title, Gtk::Window& parent) : Gtk::Dialog(title, parent, true) This should be pretty easy considering the OCAL classes already get a reference to the parent window from file.cpp. The advantage of doing this for Windows users, is that it stops your dialogs sinking down behind the inkscape desktop if someone clicks on it. Best regards Joel ---------------------------------------- From: "Bruno Dilly" <bruno.dilly@...400...> Sent: 19 August 2007 10:54 To: joel@...1709... Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] inkscape/trunk/src/ui/dialog OK Joel, I will do it soon. Thanks for the help =) On 8/19/07, joel@...1709... wrote: > I figured out what the problem was now. In my version, I made changes in > file.cpp, which I managed to miss comitting. I'm very sorry for all the > inconvenience. I assumed you were asleep, and I was hoping to slip the > change in quickly before you woke up - well that worked out just great! > > On the subject of file.cpp, the line in the current SVN version > exportDialogInstance = > Inkscape::UI::Dialog::FileExportToOCALDialog::create( > was > exportDialogInstance = new > Inkscape::UI::Dialog::FileExportToOCALDialog( > in my version. > > Can I suggest that you do the same, when you're ready? There's no need to > have separate dialog and impl classes in this case. If possible I suggest > you begin to merge the functionality of the two classes, do away with the > class factory, and just expose the constructor directly. This sounds like a > big deal, but actually it only took me about 10 minutes to do. > > Hope that helps > > Best Regards > Joel > > ________________________________ > From: "Bruno Dilly" > Sent: Sunday, August 19, 2007 10:09 AM > To: joel@...1709... > Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] > inkscape/trunk/src/ui/dialog > > But I think I didn't erased any modification. > > I just included in the file.cpp you have commited the following itens: > - an #include "ui/dialog/ocaldialogs.h" > - the password verification inside the export to ocal function > > But if you think is necessary to revert, do it, and I will fix it > later, if necessary. > > On 8/19/07, joel@...1709... wrote: > > Well it's good that you fixed it. I'm confused though, because I tested > and > > compiled my revised version *several* times. Did you guys try running > > ./autogen ? Now file.cpp needs to be reverted, as my version did away with > > the class factories. > > > > ________________________________ > > From: Jon Phillips > > Sent: Sunday, August 19, 2007 6:30 AM > > To: Bruno Dilly > > Subject: Re: [Inkscape-devel] [Inkscape-cvs] SF.net SVN: inkscape: [15827] > > inkscape/trunk/src/ui/dialog > > > > On Sun, 2007-08-19 at 02:11 -0300, Bruno Dilly wrote: > > > I was doing the same thing as Joel, and I was including the login > > > dialog used to export to ocal. > > > > > > So I commited my ocaldialogs.ccp and ocaldialogs.h, and now things look > > fine. > > > > Whoa, you guys gotta inter-communi-kate ;) > > > > Jon > > > > > On 8/19/07, MenTaLguY wrote: > > > > Joel, your recent commit appears to have broken the build. > > > > > > > > Please fix it so we can get back to work. > > > > > > > > Thanks, > > > > > > > > -mental > > > > > > > > On Sat, 2007-08-18 at 17:29 -0700, > > joelholdsworth@...58... > > > > wrote: > > > > > Revision: 15827 > > > > > > > > http://inkscape.svn.sourceforge.net/inkscape/?rev=15827&view=rev > > > > > Author: joelholdsworth > > > > > Date: 2007-08-18 17:29:36 -0700 (Sat, 18 Aug 2007) > > > > > > > > > > Log Message: > > > > > ----------- > > > > > Separated the OCAL import and export dialogs into their own source > > file - ocaldialogs.cpp and ocaldialogs.h > > > > > > > > > > Modified Paths: > > > > > -------------- > > > > > inkscape/trunk/src/ui/dialog/Makefile_insert > > > > > inkscape/trunk/src/ui/dialog/filedialog.cpp > > > > > inkscape/trunk/src/ui/dialog/filedialog.h > > > > > > inkscape/trunk/src/ui/dialog/filedialogimpl-gtkmm.cpp > > > > > inkscape/trunk/src/ui/dialog/filedialogimpl-gtkmm.h > > > > > > > > > > Added Paths: > > > > > ----------- > > > > > inkscape/trunk/src/ui/dialog/ocaldialogs.cpp > > > > > inkscape/trunk/src/ui/dialog/ocaldialogs.h > > > > > > > > > > > > > > > This was sent by the SourceForge.net collaborative development > > platform, the world's largest Open Source development site. > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > This SF.net email is sponsored by: Splunk Inc. > > > > > Still grepping through log files to find problems? Stop. > > > > > Now Search log events and configuration files using AJAX and a > > browser. > > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > _______________________________________________ > > > > > Inkscape-cvs mailing list > > > > > Inkscape-cvs(a)lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-cvs > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > > > Still grepping through log files to find problems? Stop. > > > > Now Search log events and configuration files using AJAX and a > browser. > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > _______________________________________________ > > > > Inkscape-devel mailing list > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > Inkscape-devel mailing list > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > -- > > 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... > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > >

2 1

Edit clip with node tool
by microUgly 20 Aug '07

20 Aug '07

It occured to me today that it would be pretty intuitive to be able to edit a clipping object without having to release the clip by simply selecting the node tool. I also just now seen a post that suggested this is already the plan. I'm just curious if any work is currently being done on this or if it's something that more likely to be added in later versions. -- View this message in context: http://www.nabble.com/Edit-clip-with-node-tool-tf4296255.html#a12229067 Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 1

function plotter broken
by bulia byak 19 Aug '07

19 Aug '07

Help requested from Python extension developers - in SVN, the function plotter dialog is broken: File "/usr/local/share/inkscape/extensions/funcplot.py", line 115, in drawfunction dy0 = (y1 - y0)/ds TypeError: unsupported operand type(s) for -: 'str' and 'str' I have no idea what is wrong and why it worked before. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

Re: [Inkscape-devel] Import from OCAL feature
by joel＠...1709... 19 Aug '07

19 Aug '07

Another point about OCAL export. It seems that both of us are working on filedialog.cpp, where I notice you've added two new classes FileImportFromOCALDialog and FileExportToOCALDialog to the file which already has three classes FileOpenDialog, FileSaveDialog and FileSaveDialog. I havn't been able to try the latest bits yet, but am I right in thinking that these OCAL dialogs are not file dialogs in the sense that they allow you pick a file from the file system? If this is the case, then they really don't belong in filedialog.cpp. Basically I'm hoping to get inkscape to support native file dialogs for various platforms (Windows, MacOS etc). filedialogs.cpp is the place where the class factories for the platform specific dialog implementations will be, with platform specific implementations all located within separate files. This is why I recently renamed the class FileSaveDialogImpl to FileSaveDialogImplGtk and put it in a separate file, because there's soon to come a FileSaveDialogImplWin32; and maybe one day someone will add a FileSaveDialogImplMacOS or whatever. However, you don't need to do all that for the ocal dialogs. You certainly don't need to have an addition class FileImportFromOCALDialogImplGtk; because noone should ever implement a FileImportFromOCALDialogImplWin32 or a FileImportFromOCALDialogImplMacOS or a FileImportFromOCALDialogImplBeOS! The other problem IMHO is that even before FileImportFromOCALDialog and FileExportToOCALDialog came along, when filedialogs.cpp had only 3 class implementations, that was still 2 too many*! So for these reasons I recommend you relocate these classes to another file maybe called ocaldialogs.cpp and ocaldialogs.h or something. You can also do away with both FileExportToOCALDialogImpl and FileImportFromOCALDialogImplGtk moving all their functionality into FileImportFromOCALDialog and FileExportToOCALDialog; because there will never be platform specific implementations of these dialogs. I hope this helps Best regards Joel * Soon I'm hoping to relocate FileExportDialog to another file, because it's really quite a different beast from FileOpenDialog and FileSaveDialog. ---------------------------------------- From: "Bruno Dilly" <bruno.dilly@...400...> Sent: 18 August 2007 18:31 To: "bulia byak" <buliabyak@...400...> Subject: Re: [Inkscape-devel] Import from OCAL feature On 8/18/07, bulia byak wrote: > On 8/18/07, Bruno Dilly wrote: > > bulia, to select the row: if you are using the keyboard you must press > > enter, and if you are using the mouse you must double click. > > Hmm, I'm afraid this must not be documented - it must be fixed instead > :) It's very unintuitive and plain wrong: single click must select, > double click or Enter must open selected (closing the dialog). > OK, I will change it > Anyway, now that I double click, I can import something, but only PNG > files. Any SVG file fails to show or open, writing in the console: > > (inkscape:23667): glibmm-CRITICAL **: > unhandled exception (type Glib::Error) in signal handler: > domain: gdk-pixbuf-error-quark > code : 3 > what : Couldn't recognize the image file format for file > '/tmp/johnny_automatic_pen.svg' > I couldn't reproduce the bug. Everything is working fine here, I've imported a lot of SVG files, including johnny_automatic_pen.svg. Could you make a test for me? Try to import the file directly from /tmp/, with the Import feature. Is it working for you? Do you have any other information that you think could help me to find what is happening? > By the way, it would be nice to have a line added to the dialog that > would show some information about the selected image: filename, > format, file size, date, etc. Good idea, I will see it later > > -- > bulia byak > Inkscape. Draw Freely. > http://www.inkscape.org > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

4 3

LPE: applying skeletal strokes breaks path
by Vladimir Savic 19 Aug '07

19 Aug '07

Guess it's better to start with example then explanation: 1) draw rectangle, convert it to 4 node path (ctrl+shift+c) and copy it (ctrl+c) 1a) fill it with black color 2) draw 2 point bezier line 3) open LPE editor (ctrl+shift+7) 4) pick Skeletal Stroke, apply it and paste (ctrl+v) from clipboard 5) chose Single, stretched Expected: filled four node path Result: broken path which can't be filled. Because there's no way to see how many nodes resulting path has it must be converted to regular path (ctrl+shift+c). And then it's easily noticeable that path is broken in many ways: there are too many nodes (expected 4) and shape is badly broken! Illustrative screenshots attached! Regardes, Vlada

2 3