- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] docs
by Joshua Facemyer / Impressus Art 18 Sep '07

18 Sep '07

On a similar topic as documentation, I'd be happy to add some news items to the main page from time to time. I know that before I read the dev list I would get discouraged by lack of posted news, but there's so much going on. How would I contribute news items? What kinds of items would be desirable? JF

2 1

Live effect preview
by unknown＠example.com 18 Sep '07

18 Sep '07

Thanks for adding the checkbutton Ted! But still, (all) effects crash for me on WinXP. Now that I have checked the "live preview" box, I get instant crashes when opening any effect dialog. So I cannot even uncheck the box to make inkscape work :( Could you perhaps add a #define to disable live preview on windows until it works? Does this crash for all Windows users? Or only for me? Johan

6 38

Re: [Inkscape-devel] Hi
by Joshua Blocher 17 Sep '07

17 Sep '07

No, I mean select it with the selection and transformation tool (F1), the Trace Bitmap has to have a target bitmap selected to trace use the above tool to select it then trace bitmap. Joshua L. Blocher verbalshadow On 9/14/07, Andreas.berg3@...128... <andreas.berg3@...128...> wrote: > P.S. or did you ment some different like import, > or afterwords mark the Bitmap as a path? > > I tried both......... > > Best Regards > > Andreas > Am 13.09.2007 um 22:55 schrieb Joshua Blocher: > > > Andreas, > > > > It sound like you didn't select the bitmap before tracing/vectorizing. > > Please check to see that is the problem. > > > > Joshua L. Blocher > > verbalshadow > > > > On 9/14/07, Andreas.berg3@...128... <andreas.berg3@...128...> wrote: > >> Hello im not really used to write in dev Lists, i even cant read > >> source code :o) > >> > >> OK i have a Problem and maybe a Bugreport, so see im an not that > >> much advanced User (like at my english, it says everythin :o) > >> > >> Id load today Inkscape, to try out, my aim is it to Trace or > >> Vectorize ,or how ever its called in english, an Bitmap or better an > >> Gif Image. > >> My first Step is it to Import it, then i open the Option "Bitmap > >> Vectorize" (i use it in German, so .....) and after i choose all my > >> preferences i click on action, but it seams like nothing hapens. > >> Id search and look at all manuals ( like i should do :o) did wait for > >> over 10 Min. but, guess what, yeah nothin happens. > >> So i dont know if i do some wrong and when it is like that i really > >> cant expect what it could be. > >> > >> OK, Im using Mac OS X, 10.4.10 on an Intel Mac, yeah i know its > >> running under X11 and i have to wait, but it starts up pretty fast. > >> > >> I really dont even know if its the right Place to talk about that, > >> but i hope so, if not exuse my please, but tell me tahn to where it > >> would be. > >> > >> If the one who answeres me is or know German, i would prefer that, > >> cause english is not my first Language, and im writing like > >> Simpleton, lol > >> > >> > >> Best Regards > >> > >> > >> > >> Andreas Berg > >> > >> --------------------------------------------------------------------- > >> ---- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Inkscape-devel mailing list > >> Inkscape-devel(a)lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >> > >

4 4

initial inkscape user feedback from a regular illustrator user.
by Andy Fitzsimon 16 Sep '07

16 Sep '07

G'day guys, Someone new has started here in Brisbane who comes from a heavy illustrator background. During her first day using Inkscape she's written up this short document mentioning her initial reactions. a good quote to summarize: "I can find this stuff out by reading the manual. I'm just telling you what isn't immediately apparent enough as I feel like it ought to be." ------------------ Becc's Inkscape Hassles -------- Magnification in/out buttons: Wanting to zoom out, I hit the button showing the magnifying glass with a minus sign on it, then clicked on the page several times waiting for it to zoom out the same way it does when you've clicked on the button showing the magnifying glass with + sign on it. It didn't, but instead zoomed in. These buttons shouldn't imply they offer in/out aspects of the same tool but not behave consistently with this implication. Zoom level indication: The level of magnification indicator down beneath my work is out of whack with the zoom tools being up in the menu above it: I don't expect to hit a button on one menu and have to look to a field on another one to see the changes it's effected. At the time that I performed the above zooming in and out, I had nothing on my page and was zoomed in to a level where I couldn't see the edges of the page. As such, I was wanting feedback letting me know that my actions were having some kind of effect. (I expected this to be zooming me out, which turned out not to be the case – I was still zooming in, as mentioned – but any feedback would've been helpful in letting me know this button wasn't working as expected and that I should thus adjust my approach.) Ditto with the related shortcuts: I can hit Shift++ but not Shift+-, which is inconsistent. I can use a scrollbar to move my view horizontally but not vertically. Makes moving my focus difficult. (NB: I later worked out I can scroll up and down using the mouse wheel; okay, but having a scrollbar for only one kind of pan when both kinds of pans are possible is inconsistent and leads one to believe, as I did earlier, that only one kind of panning is possible – otherwise, surely both would be represented onscreen in the same way, y'know? Also, what do you do if you don't have a wheel mouse?) I'm not sure what to hold down to create a perfect circle. I seem to have managed it accidentally by holding down Shift one time, holding down Ctrl another time, and holding both together another time, but none of these seem to create a perfect circle consistently: in each case switching to an oval occurs if I'm not very careful about where I'm dragging my pointer while I have the appropriate key/s held down. If I want to select nodes, I seem to not only have to use the "node edit" tool but must first select the entirety of the object(s) the nodes are a part of in order to be able to do so. This slows me down by adding in a step that doesn't seem necessary or logical. It also took me some time to work out that the problem wasn't simply that the node selection tool doesn't work – I really only kept trying because I knew from having created that teardrop shape when you were standing there assisting me that nodes could be selected and edited somehow – which is going to present to potential converts from, er, say, Illustrator, as bugginess and incompleteness. Please let me rotate my object as easily as I can resize it, without opening the Transform menu. Sometimes I don't know how many degrees I want to rotate it, and sometimes I just want to turn it 'round 'til it looks about right, so need to be able to wiggle it around experimentally. :) So, I'm beginning to form an idea of this program (and point this out in the assumption that any user will do similarly) as having not just paths with nodes like Illustrator does, but also having something called "objects" that fit into all of this somewhere. My immediate difficulty with that is this: I'm working at present with a shape that's made up of a path. However I wouldn't know it to look at it when selected, because the fact that it has a path outlining it isn't readily apparent unless I not only select it but double-click on it. I don't recall having to ever double click on something to edit it. Is showing its path possible with just one click (also, can I see the wire line of the path rather than just the nodes on it when I do so? I can't make out the shape of what I'm working on when it's over/under an object of the same colour!)? Could doing this perhaps serve also to allow the user to easily see what's a shape and what's a path? As it is, I'm still having difficulties conceptualising what the building blocks of this program are (which is important because they're what I'm going to use to develop my drawings etc as a user), and I wonder if making the differences between the two more readily discernable might assist in getting that across... Is the node edit tool the only way I can alter a line once I've drawn it? I'm accustomed to being able to select it and alter it with the pencil – particularly when I'm using a graphics tablet, this is my preferred method of working, cuz it makes using a computer to draw just like using a pencil and paper. :( I've hit a numeral a few times when meaning to type something or enter a size or angle of a rotation into a text field and instead found my view suddenly changed. This isn't a bug – I've obviously had the focus in a place other than where I thought it was – but a suggestion that the numbers on the keyboard not be used to change the view without the use of the Ctrl or Shift key consistent with usual shortcut behaviour. Fill and Stroke colours are taking up so much real estate in their respective menus that they shouldn't need. I know you're trying to supply optimum control, but I'm being overwhelmed by details here when all I want is to select an appropriate shade of pink to colour the pieces of my exploded brains. Clicking on a colour swatch on the main screen shouldn't open up a menu offering me options to choose between fill, stroke, and stroke style, and then (once I've worked out that I should stay inside the 'fill' tab of that menu) decide between what kind of fill, whether I want to use RGB or CMYK or Pantone, the colour(s) amongst those I want to use, etc, all at once. I just want to change the colour. Wouldn't it make more sense when I click on a swatch of colour to open up a menu offering me only colour options? Sure, the colour is an attribute of a background; so offer the other background options in the menu's other (unfocused) tabs – not options having to do with strokes or stroke style. As with the Fill option, the Stroke options are taking up a lot of space because they're providing a lot of detail I don't immediately need if I'm just clicking on, say, a swatch (in which case I want to change the colour), or on a I can't seem to shift objects up and down within a layer. Does this mean that if I don't want to employ layers for something that before I start drawing I need to think about the order in which I need to draw objects, starting from the bottom up? :-/ Er... I can't scroll left to right using that scroll bar I mentioned earlier! I can't remember if it was working then; it certainly isn't now. Joining two path ends together would be handy – something I use all the time When I try to copy a style using the eyedrop tool, as an Illustrator user I'm expecting both fill and stroke to be applied to the object I'm working with. At the moment I'm getting only fill. Since I do have the whole object selected and not just its fill, I'm not finding any logical reason why both fill and stroke settings shouldn't be getting copied over. ------------

3 5

Re: [Inkscape-devel] Scheme Scripting Console
by Ted Gould 16 Sep '07

16 Sep '07

On Sun, 2007-08-12 at 18:47 -0500, Samuel A. Rebelsky wrote: > I'm the faculty member who supervises David and Soren's work. Thanks > for your regular and rapid feedback on their work! I hope we'll find > a way to get some Scheme scripting console into InkScape, even if > it's not the one that they've written. Anyway, I thought I should > respond to your two questions. Great to meet you. I don't see any major barriers to using theirs, just a couple details we need to work out. > I don't have much to say about the document locking issue; if there's > a better approach, I'm sure that they'd be happy to adopt it. What would you guys think about building the patch without this? I know it'd be slower, but then we could get some of the code into the tree so that you'd have less of a branch to maintain. > In terms of the TinyScheme issue, as best as I can tell, TinyScheme > semms to have replaced SIOD as the implementation language for Script- > Fu in the Gimp, starting with 2.3 (development) and 2.4 (release, > eventually), but I'm working as an outsider. I'm pretty sure the > discussion was in mid-2006. Let's see ... the developers mailing > list had a note about the replacement in week 42. <snip> > If you'd prefer that Soren and David use guile, rather than > TinyScheme, as the base implementation of Scheme for their InkScape > scripting console, that's fine with me. (And probably with them.) > However, it will delay their work somewhat, since they're starting > classes again, and their available time is going away. It really isn't as much about which Scheme interpreter, as much as how to include it. The problem that we run into is that if we include it in our source tree we end up maintaining that code. If we keep it as an external dependency, someone else maintains it. I like less work if possible. :) It would also make sense that if GIMP is using the same interpreter that we are, we make it an external package. That way bugs can be fixed in one place. From some of the stuff I've been reading on the GIMP webpage it seems that their version of TinyScheme is patched to work better with GTK+ (UTF-8 fixes). Is that the version you guys have included? > p.s. Your message to the Gimp developers' list did get posted, it's > at http://www.gimpusers.com/mailmsg.php?1186687639.4436.4.camel%40bender Still haven't received any responses. I'll see what I can find out. I'll wait for "Monday" to finish around the world first :) --Ted

3 3

misc dock issues
by bulia byak 16 Sep '07

16 Sep '07

Hi Gustav, some glitches and questions as of rev 16035: Docked dialogs don't scroll to be visible when I call them, if the dock contains many dialogs scrolled down. Is this fixable? Hightlighting the title of the dialog which was just called by a shortcut is nice, but it does little else - the keyboard focus is still not in the dialog. Or at least, I can't use Tab to travel between widgets in the dialog as I was able in the dialog as a top-level window - Tab works to select object on canvas no matter what. On the other hand, the accelerator keys (underlined in labels) work indiscriminately across all dialogs and all UI in general. For example, select an object, open fill&stroke and switch to HSL tab, then press Alt+H. The first time, the Help menu is opened; the second time, focus jumps to the H field in the dialog. This is a really bad problem - few people use accelerators in dialogs but many call menus by Alt+letter, so this needs to be fixed somehow. Is it possible to limit the scope of the accelerators to the dialog only, so that they only work when some widget in the dialog has focus? By the way, if I can highlight the dialog with its shortcut, it would be logical if it was also highlighted when I click some widget in it, or just click on its title bar. Is this feasible? Press Ctrl+Shift+W - the swatches dialog pops up. Press it again and you get "** Message: Failed to find an existing dialog". Works with other dialogs but not this one. Is it possible to not show the separators between dialogs in the dock with resize handles when resizing is not possible? This is misleading. Open several dialogs, then open fill&stroke, iconify it, then restore. It works but I get in the console: (inkscape:3948): GLib-GObject-WARNING **: value "-313" of type `gint' is invalid or out of range for property `preferred-height' of type `gint' Now that you've replaced them, can you remove the obsolete fill&stroke code from src/dialogs? Note that the selected-style.cpp calls sp_object_properties_fill and sp_object_properties_stroke, which open the old (non-gtkmm) dialog and switch to the corresponding tab. Can you provide similar accessor functions for the gtkmm docked dialog and replace these calls? -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

4 4

I'm back!
by Gail Carmichael 15 Sep '07

15 Sep '07

As you may have noticed from an earlier email, I'm more or less back from all that wedding stuff. The ceremony was wonderful and the honeymoon trip to the Dominican Republic really fun! Email me if you want to see some photos and I'll send some links. So now down to business. School is ramping up, but it looks good to be able to spend some time every week looking at Inkscape. Which is good, because I have several loose ends to take care of. I am aware of the funky newline behaviour that a few of you have logged bugs on. That will be my first priority. Once that's ironed out, I will be cleaning up my last patch from SoC. Finally, once that's checked in and working, I will finish the end goal with that code, namely sorting out the UI lists to be what we want and looking into Pango limitations with those folks. No idea how long that will all take, but will be definitely making a good effort to get the most urgent stuff done as soon as I can. Cheers, Gail

2 1

object properties
by Alexandre Prokoudine 15 Sep '07

15 Sep '07

Hi, I have a very tough question, so feel free to punch me for that one :) What do we actually plan to do with Object Properties palette? It looks like it wasn't touched for ages. Recently I had a talk with a newbie user and he told me that he expected seing there more properties, both "global" and "specific". In that particular case he couldn't figure out how to change amount of an already created polygon's sides and he expected to see that in Object Properties palette. Then there was another feature request to make it possible choosing what properties of selected objects can be changed. E.g. in a selection of 25 objects you can have 12 objects which should not lose either fill or stroke or opacity or any specific for this type of objects property or any combination of the above, when you change it for the whole group. And as you know ;-) Inkscape, unlike Scribus, doesn't store changes per object within a session, so you can't aply changes to a group and then undo it for individual objects. So the second part of the question is whether we can make a better use of the Object Properties palette. In addition to what there already is in that palette we could add two groups of options: 1. Global options, i.e. Fill, Stroke, Opacity, Filters. 2. Specific options, i.e. the ones from tools options toolbar. For selections with multiple objects of different types (e.g. 2 stars and 3 rectangles) specific options would be greyed out. Each option would have a checkbox to allow/forbid changes to it, with 3 positions: yes, no, fuzzy (when at least two of the selected objects have different values, gtk supports it). Am I daydreaming? :) Alexandre

3 4

Hi
by Andreas.berg3＠...128... 15 Sep '07

15 Sep '07

Hello im not really used to write in dev Lists, i even cant read source code :o) OK i have a Problem and maybe a Bugreport, so see im an not that much advanced User (like at my english, it says everythin :o) Id load today Inkscape, to try out, my aim is it to Trace or Vectorize ,or how ever its called in english, an Bitmap or better an Gif Image. My first Step is it to Import it, then i open the Option "Bitmap Vectorize" (i use it in German, so .....) and after i choose all my preferences i click on action, but it seams like nothing hapens. Id search and look at all manuals ( like i should do :o) did wait for over 10 Min. but, guess what, yeah nothin happens. So i dont know if i do some wrong and when it is like that i really cant expect what it could be. OK, Im using Mac OS X, 10.4.10 on an Intel Mac, yeah i know its running under X11 and i have to wait, but it starts up pretty fast. I really dont even know if its the right Place to talk about that, but i hope so, if not exuse my please, but tell me tahn to where it would be. If the one who answeres me is or know German, i would prefer that, cause english is not my first Language, and im writing like Simpleton, lol Best Regards Andreas Berg

8 9

swatches palette
by Alexandre Prokoudine 15 Sep '07

15 Sep '07

Hi, Is some work on Swatches palette planned? Any idea why it has both horizontal and vertical scrollbars enabled by default? They make it look not so polished :( Alexandre

2 1

compile of nodepath in latest inkscape development version fails with gcc-3.3.4
by E.J. Neafsey 14 Sep '07

14 Sep '07

I have successfully compiled inkscape 0.45.1 on my linux machine using gcc-3.3.4. When I tried to compile inkscape-16051 today, it failed while compiling nodepath, giving the error messages below. Can this be fixed? Thanks. E.J. Neafsey eneafse@...1805... ========================================================================= make all-recursive if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/freetype2 -I/usr/local/include -DORBIT2=1 -pthread -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include -I/usr/include/freetype2 -DXTHREADS -I/usr/include/freetype2 -I/usr/local/include/libpng12 -I/usr/local/include/gtk-unix-print-2.0 -I/usr/local/include/gtk-2.0 -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include -I/usr/local/include/poppler -DXTHREADS -I/usr/include/freetype2 -I/usr/local/include/libpng12 -I/usr/local/include/poppler/glib -I/usr/local/include/poppler -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/cairo -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pango-1.0 -I/usr/X11R6/include -DPOTRACE=\"potrace\" -pthread -DXTHREADS -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/freetype2 -I/usr/local/include/libpng12 -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/cairomm-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/cairo -I/usr/local/include/atk-1.0 -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/X11R6/include -I../cxxtest -Wall -Wformat-security -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -D_FORTIFY_SOURCE=2 -Wno-unused-parameter -g -O2 -MT nodepath.o -MD -MP -MF ".deps/nodepath.Tpo" \ -c -o nodepath.o `test -f 'nodepath.cpp' || echo './'`nodepath.cpp; \ then mv -f ".deps/nodepath.Tpo" ".deps/nodepath.Po"; \ else rm -f ".deps/nodepath.Tpo"; exit 1; \ fi In file included from live_effects/effect.h:16, from live_effects/lpeobject.h:13, from nodepath.cpp:50: 2geom/path.h:72: warning: `virtual Geom::Curve* Geom::Curve::reverse() const' was hidden 2geom/path.h:310: warning: by `Geom::Curve* Geom::SVGEllipticalArc::reverse(double, double) const' 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::begin()': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:469: error: within this context 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::end()': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:470: error: within this context 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::begin() const': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:475: error: within this context 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::end() const': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:476: error: within this context 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::end_open() const': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:478: error: within this context 2geom/path.h: In member function ` Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > > Geom::Path::end_closed() const': 2geom/path.h:373: error: `Geom::BaseIterator<IteratorImpl>::BaseIterator(const IteratorImpl&) [with IteratorImpl = __gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]' is private 2geom/path.h:479: error: within this context 2geom/path.h: In member function `void Geom::Path::insert(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, const Geom::Curve&)': 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:565: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:565: error: within this context 2geom/path.h: In member function `void Geom::Path::erase(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >)': 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:591: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:591: error: within this context 2geom/path.h: In member function `void Geom::Path::erase(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >)': 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:595: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:595: error: within this context 2geom/path.h: In member function `void Geom::Path::replace(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, const Geom::Curve&)': 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:601: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:601: error: within this context 2geom/path.h: In member function `void Geom::Path::replace(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, const Geom::Curve&)': 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:613: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:613: error: within this context 2geom/path.h: In member function `void Geom::Path::insert(Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >, Geom::BaseIterator<Impl>, Geom::BaseIterator<Impl>) [with Impl = __gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > >]': 2geom/path.h:436: instantiated from here 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:576: error: within this context 2geom/path.h:436: instantiated from here 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve* const*, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:576: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:578: error: within this context 2geom/path.h:375: error: `__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > Geom::BaseIterator<__gnu_cxx::__normal_iterator<Geom::Curve**, std::vector<Geom::Curve*, std::allocator<Geom::Curve*> > > >::impl_' is private 2geom/path.h:578: error: within this context make[2]: *** [nodepath.o] Error 1 make[2]: Leaving directory `/usr/local/src/inkscape/inkscape-16051/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/inkscape/inkscape-16051' make: *** [all] Error 2 ==============================================================================

3 4

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 16, Issue 23
by Andreas.berg3＠...128... 14 Sep '07

14 Sep '07

I dont know if i have to make a mention on this, but if you guys need to test something or need feedback how or if it runs (and you tell me how to do :o) I will help and do as far i can, cause im pretty thankfull that you do such a great job and i would do my part as i could to........ Hopefully someone can even understand what i wnat to say, with my broken english lol Best Regards Andreas P.S. i use MacBook so IntelMac and 10.4.10 Mac OS X Am 14.09.2007 um 19:43 schrieb inkscape-devel- request(a)lists.sourceforge.net: > Send Inkscape-devel mailing list submissions to > inkscape-devel(a)lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > or, via email, send a message with subject or body 'help' to > inkscape-devel-request(a)lists.sourceforge.net > > You can reach the person managing the list at > inkscape-devel-owner(a)lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Inkscape-devel digest..." > > > Today's Topics: > > 1. Re: NEW: XSLT Input/output extension support (Ted Gould) > 2. Re: Hi (David Christian Berg) > 3. Re: compile of nodepath in latest inkscape development > version fails with gcc-3.3.4 (E.J. Neafsey) > 4. Re: printing (Bryce Harrington) > 5. More problems compiling in Windows (Joel Holdsworth) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 13 Sep 2007 21:27:24 -0700 > From: Ted Gould <ted@...11...> > Subject: Re: [Inkscape-devel] NEW: XSLT Input/output extension support > To: bulia byak <buliabyak@...400...> > Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> > Message-ID: <1189744044.5343.10.camel@...1636...> > Content-Type: text/plain; charset="us-ascii" > > On Wed, 2007-09-12 at 11:08 -0700, Ted Gould wrote: >> On Wed, 2007-09-12 at 12:55 -0300, bulia byak wrote: >>> First, this is really great, but whan I write an email with a >>> NEW: in >>> subject, that email is usually just a copy of what I just added >>> to the >>> Release Notes :) Please always describe all your additions there in >>> detail (and please fill in a wpg library placeholder marked as yours >>> too). >> >> Wasn't WPG added in 0.45? > > I looked back, and WPG was in 0.45. I'm going to remove the entry > from > the release notes. > > --Ted > >

1 0

printing
by Alexandre Prokoudine 14 Sep '07

14 Sep '07

Hi, According to 0.46 release notes we now use Gtk 2.10+ printing dialog. However, the --with-gnome-print option is still present in ./configure script and doesn';t actually work: http://pastebin.ca/696577 Do we really need gnome-print integration now? And a more difficult question: will gtk provide us color managed printing whenever color management is implemented in Inkscape? Alexandre

2 1

Re: [Inkscape-devel] [Inkscape-user] Can't get email confirmation from Inkscape Wiki
by bulia byak 13 Sep '07

13 Sep '07

On 9/13/07, Ben Bullock <benkasminbullock@...400...> wrote: > Can anyone help with the following? > > I started an account on the Inkscape wiki but it won't send me the > confirmation email. I've tried four times to get the email. Yes, others reported the same problem. Please someone fix this ASAP! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

2 1

Please do not mark empty string as translatable
by Luca Bruno 13 Sep '07

13 Sep '07

Hi, I just commited rev16059, basically doing s/_("")/("")/ where due. It looks like some developers are used to leave some labels/tooltips/strings empty, but mark them as translatable. This already surfaced on -translator some times ago (see [1]), but I was heavily bitten again today, so I fixed it. Basically gettext has a bad behaviour wrt empty strings, and it replaces them with the .po header. Results are these: http://img132.imageshack.us/img132/4834/emptystringwi6.png So please *avoid* marking empty strings, or really weird things will happen in localisation. Cheers, Luca [1] http://sourceforge.net/mailarchive/message.php?msg_name=733f2c730708271231x… -- .''`. ** Debian GNU/Linux ** | Luca Bruno : :' : The Universal O.S. | luca.br(AT)uno.it `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Proud Debian GNU/Linux User

2 1

Inkscape native on OS X... almost
by jiho 12 Sep '07

12 Sep '07

hello all, Motivated by all the good things I saw about gtk on os x these days and repulsed by all the statistics I should be doing for my real life work, I gave a try at compiling inkscape with GTK native using MacPorts (so not using the all in one build script that Michael cook up a little while ago). MacPorts is the OS X equivalent of apt-get, portage, yum or whatever. We use it to provide Inkscape dependencies currently and it is very convenient to compile Inkscape that way. It is both easy (all second level dependencies are managed by macports) and economic (the libraries I compile for inkscape can be used in other projects). I wanted to keep this ease of use and to leverage the work of others, so I wanted to keep using MacPorts. The steps: 1- MacPorts includes native versions of gtk and cairo, which can be installed with: port install cairo +quartz gtk2 +quartz (gentoo and bsd users will recognize the "variants" switches added to both packages). there is a small bug in gtk which is known and solved by the patches in this ticket, at MacPorts: http://trac.macports.org/projects/macports/ticket/12566 hopefully they will commit this soon... but the bug report is quite old already. 2- Other libraries compiled against gtk or cairo need to be recompiled to use these new variants. namely: port -f uninstall cairomm gtkmm pango port install cairomm gtkmm pango this could possibly be solved by a clever use of upgrade when compiling gtk2 and cairo but I did not bother (I should have though...) 3- then compile inkscape from fresh make distsclean cd packaging/macosx/ change the compilation options to remove "--enable-osx-app" for now and then update, configure, build and install: ./osx-build-sh u a c b i compilation goes smoothly for latest svn... great great great!!! Now, on for the hard part: 4- run inkscape cd ../../Build/bin/ ./inkscape and here: (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Gdk-WARNING **: Unsupported cursor type 14, using default 2007-08-31 16:18:34.382 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fef7a0 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.382 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fee200 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.386 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14ffa730 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.390 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fb9830 of class GdkQuartzWindow autoreleased with no pool in place - just leaking (inkscape:20759): Gdk-WARNING **: Unsupported cursor type 14, using default CGBitmapContextGetBitsPerPixel: invalid context cairo.c:91: failed assertion `status > CAIRO_STATUS_SUCCESS && status <= CAIRO_STATUS_LAST_STATUS' Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. (inkscape:20759): GLib-WARNING **: g_main_loop_run(): called recursively from within a source's check() or prepare() member, iteration not possible. Aaaargh. Anyway, the good points are that it is now quite easy to get GTK native in our regular building system and that Inkscape builds and links fine against it! Now, about the crash, it may well be that my system is still kind of dirty (I have some native things but the rest of the libraries are the old ones) but I think it is more likely a bug in cairo +quartz. I'll be happy to try to track it down and see if it is fixable in Inkscape or if this needs to be solved ahead. From the gdb backtrace below it seems to involve pango_cairo_renderer_draw_glyph. If that rings a bell to anyone I'll be glad to know what you think or provide more info where it is needed. I will also probably try to reinstall a separate macports hierarchy this week end and reinstall everything with gtk native there, to be sure the dependencies are clean. We'll see. Anyway, even if I only saw a blank window instead of Inkscape UI, I was still quite happy to see it without the X11 icon in the dock!! Cheers, Backtrace: #0 0x9003d66c in kill () #1 0x9010e8cf in raise () #2 0x9010d422 in abort () #3 0x02000356 in __eprintf () #4 0x01f9d893 in _cairo_error () #5 0x01f9d8ab in _cairo_set_error () #6 0x01dbe0f6 in pango_cairo_renderer_draw_glyphs () #7 0x01dddd4c in pango_renderer_draw_glyphs () #8 0x01dbe6e4 in _pango_cairo_do_glyph_string () #9 0x01c9bae4 in gdk_pango_renderer_draw_glyphs () #10 0x01dddd4c in pango_renderer_draw_glyphs () #11 0x01ddf09c in pango_renderer_draw_layout_line () #12 0x01ddf2b9 in pango_renderer_draw_layout () #13 0x01c9d99a in gdk_draw_layout_with_colors () #14 0x01c9dca7 in gdk_draw_layout () #15 0x01a17406 in gtk_default_draw_layout () #16 0x01a1a113 in gtk_paint_layout () #17 0x01966e1c in gtk_label_expose () #18 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #19 0x01e0a634 in g_closure_invoke () #20 0x01e1b3e3 in signal_emit_unlocked_R () #21 0x01e1c857 in g_signal_emit_valist () #22 0x01e1d177 in g_signal_emit () #23 0x01ae03c3 in gtk_widget_event_internal () #24 0x01adffdb in gtk_widget_send_expose () #25 0x018ce122 in gtk_container_propagate_expose () #26 0x018cdcaa in gtk_container_expose_child () #27 0x01a1d7fe in gtk_table_forall () #28 0x018cbab6 in gtk_container_forall () #29 0x018cddad in gtk_container_expose () #30 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #31 0x01e0a634 in g_closure_invoke () #32 0x01e1b3e3 in signal_emit_unlocked_R () #33 0x01e1c857 in g_signal_emit_valist () #34 0x01e1d177 in g_signal_emit () #35 0x01ae03c3 in gtk_widget_event_internal () #36 0x01adffdb in gtk_widget_send_expose () #37 0x018ce122 in gtk_container_propagate_expose () #38 0x018cdcaa in gtk_container_expose_child () #39 0x01880aea in gtk_box_forall () #40 0x00c26ebf in Gtk::Container_Class::forall_vfunc_callback () #41 0x018cbab6 in gtk_container_forall () #42 0x018cddad in gtk_container_expose () #43 0x00ca9502 in Gtk::Widget::on_expose_event () #44 0x00ca5e8a in Gtk::Widget_Class::expose_event_callback () #45 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #46 0x01e0a634 in g_closure_invoke () #47 0x01e1b3e3 in signal_emit_unlocked_R () #48 0x01e1c857 in g_signal_emit_valist () #49 0x01e1d177 in g_signal_emit () #50 0x01ae03c3 in gtk_widget_event_internal () #51 0x01adffdb in gtk_widget_send_expose () #52 0x018ce122 in gtk_container_propagate_expose () #53 0x018cdcaa in gtk_container_expose_child () #54 0x01880aea in gtk_box_forall () #55 0x018cbab6 in gtk_container_forall () #56 0x018cddad in gtk_container_expose () #57 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #58 0x01e0a634 in g_closure_invoke () #59 0x01e1b3e3 in signal_emit_unlocked_R () #60 0x01e1c857 in g_signal_emit_valist () #61 0x01e1d177 in g_signal_emit () #62 0x01ae03c3 in gtk_widget_event_internal () #63 0x01adffdb in gtk_widget_send_expose () #64 0x018ce122 in gtk_container_propagate_expose () #65 0x018cdcaa in gtk_container_expose_child () #66 0x01880b35 in gtk_box_forall () #67 0x018cbab6 in gtk_container_forall () #68 0x018cddad in gtk_container_expose () #69 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #70 0x01e0a634 in g_closure_invoke () #71 0x01e1b3e3 in signal_emit_unlocked_R () #72 0x01e1c857 in g_signal_emit_valist () #73 0x01e1d177 in g_signal_emit () #74 0x01ae03c3 in gtk_widget_event_internal () #75 0x01adffdb in gtk_widget_send_expose () #76 0x018ce122 in gtk_container_propagate_expose () #77 0x018cdcaa in gtk_container_expose_child () #78 0x0187c3e3 in gtk_bin_forall () #79 0x018cbab6 in gtk_container_forall () #80 0x018cddad in gtk_container_expose () #81 0x018f3a4c in gtk_event_box_expose () #82 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #83 0x01e0a634 in g_closure_invoke () #84 0x01e1b3e3 in signal_emit_unlocked_R () #85 0x01e1c857 in g_signal_emit_valist () #86 0x01e1d177 in g_signal_emit () #87 0x01ae03c3 in gtk_widget_event_internal () #88 0x01adffdb in gtk_widget_send_expose () #89 0x0197b424 in gtk_main_do_event () #90 0x01cbf535 in -[GdkQuartzView drawRect:] () #91 0x933123b1 in -[NSView _drawRect:clip:] () #92 0x9331140b in -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] () #93 0x9332336f in _recursiveDisplayInRect2 () #94 0x9083eb30 in CFArrayApplyFunction () #95 0x93311613 in -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] () #96 0x93310473 in -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #97 0x93311041 in -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #98 0x9330fb78 in -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #99 0x9330f362 in -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] () #100 0x9330ec8e in -[NSView displayIfNeeded] () #101 0x9330ea32 in -[NSWindow displayIfNeeded] () #102 0x9335ed6c in _handleWindowNeedsDisplay () #103 0x9082dd6e in __CFRunLoopDoObservers () #104 0x9082ce10 in CFRunLoopRunSpecific () #105 0x9082cace in CFRunLoopRunInMode () #106 0x92ded8d8 in RunCurrentEventLoopInMode () #107 0x92decf19 in ReceiveNextEventCommon () #108 0x92dece39 in BlockUntilNextEventMatchingListInMode () #109 0x93293465 in _DPSNextEvent () #110 0x93293056 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #111 0x01cb8a86 in gdk_event_prepare () #112 0x0223faf4 in g_main_context_prepare () #113 0x022401b6 in g_main_context_iterate () #114 0x022408cd in g_main_loop_run () #115 0x0197a9f0 in gtk_main () #116 0x00c48d02 in Gtk::Main::run () #117 0x00004451 in sp_main_gui () #118 0x00158732 in Inkscape::NSApplication::Application::run () #119 0x00003357 in main () JiHO --- http://jo.irisson.free.fr/

6 10

Reverting zoomed-in files
by Maximilian Albert 11 Sep '07

11 Sep '07

Hi, when reverting a document via File->Revert, is it possible to preserve the current zoom factor and panning? If not, what would it require to implement this? It's not that I urgently need it or am particularly keen on implementing it, just figured it might be useful and thought I'd ask. Cheers, Max

2 4

Color enum purged
by Jon A. Cruz 11 Sep '07

11 Sep '07

Next step in supporting CMYK, etc, was to purge the paint enum type. Take a look to see if things are still holding up. The main reason is that we're getting to support proper SVG paint, not just the union/enum subset. That is, a paint could have both a URL and a normal color part specified, or a URL, a normal color part *and* an icc-color...

3 3

Toggling dialogs by keyboard shortcuts
by Maximilian Albert 11 Sep '07

11 Sep '07

Hi, some time ago I thought it would be nice if dialogs could be _toggled_ (as opposed to only be shown) by their corresponding keyboard shortcuts. This is especially true with the new dockable dialogs (great improvement, by the way, in case I haven't mentioned it yet :)) because they don't respond to Ctrl+W any more so that they closing them is only possible by using mouse clicks, not the keyboard alone. I tried to implement toggling but have two small questions: - What is the right entry point in the code? Should this be done in the DialogManager::showDialog() function? In this case, is there already a way to test whether a Dialog is currently visible, or do I need to add a new boolean variable to the Dialog class? - When a dialog is invoked for the very first time after startup, it seems to be present()-ed more than once so that a check for the dialog's visibility wrongly indicates that it is already being shown (thus in order to initially show a dialog, its corresponding shortcut needs to be pressed twice, which is annoying and inconsistent). What is the reason for this? And is there a less cumbersome way to circumvent it than introducing yet another boolean variable just to check whether the dialog was already shown before? Thanks for any hints, Max

2 6

selector controls
by bulia byak 11 Sep '07

11 Sep '07

I added three buttons for Select all, Select all in all layers, and Deselect to the start of the Selector's control bar. I think they are quite relevant there (at least more relevant than the z-order buttons) and are quite often used functions, especially now that with the Tweak tool you often need to select everything indicscriminately. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

Gradient bug.
by Tomasz Kobiela 10 Sep '07

10 Sep '07

Hi, I was lately monitoring gradient look and I must say in latest build it looks very good (as good as in illustrator or gimp). I was playing with inkscape build form 6 sep and I found bug with gradient. When I was preparing gradient for mask I found that gradient is cut on bottom (about 10% of gradient was cut). I made svg: http://kobi.ovh.org/kobi-theme.svg It will be easier if you will see it. On centre of image is rectangle with gradient. --- Kind regards Kobi.

1 0

inkscape eclipse page on wiki
by Richard Henwood 10 Sep '07

10 Sep '07

Hi Folks, I've been using the advice on the inkscape/eclipse page, http://wiki.inkscape.org/wiki/index.php/Using_Eclipse using Linux, I have found it necessary to run: ./autoconf.sh, ./configure before a Makefile is generated which Eclipse is happy with. Is this a requirement (or am I just incompetent) on both windows and linux platforms? If so, I will make a suitable edit to the wiki. cheers, richard

3 3

Problem with Wiki
by Thomas Worthington 09 Sep '07

09 Sep '07

Hi, Can anyone help with the Wiki? I've created an account (twworthington) and asked for the email confirmation several times both last week and this, using Opera and Firefox and this email address and my work one but nothing has appeared, so I can't add in the docs for the Alt-key mapping. Anyone have any ideas?

3 2

PDF export fails where it shouldn't
by Vladimir Savic 08 Sep '07

08 Sep '07

I've generated two very simple PDFs from very simple SVG file just to illustrate the problem. Look at attached documents... PDFsvg2pdf.pdf was generated using program svg2pdf which rely on librsvg and cairo PDF.pdf was exported directly from Inkscape PDF.svg is very simple Inkscape drawing Observe the file sizes too. Vlada

3 3

NEW: Dockable dialogs
by Gustav Broberg 07 Sep '07

07 Sep '07

I have now committed the patch [1],[2] I've been working on for quite some time. It gives Inkscape a dock panel right of the canvas on which dialogs can be docked. A part of an external library, GDL, has been included in the tree with this patch, this had to be done as GDL isn't widely available and the fact it demanded some Inkscape specific customizations. The good thing is that this implies that Inkscape's list of dependencies remains unchanged. The design of the dialog system allows the new dockable dialog behavior to exist along side the old floating dialogs behavior. If the old behavior is preferred, one can select it under Inkscape Preferences > Windows > Dialog behavior. Know issues ----------- * It doesn't work well with multiple open documents. Fixing it requires a bit of rewrite of the current dialog manager. I'll focus on doing this before the code freeze. * Resizing in-dock dialogs can be cumbersome. More specifically, one won't be able to expand a dialog placed in the dock unless all dialogs beneath it are expanded in advance. Fixing this requires some changes in GDL, I've got it somewhat working, but decided that it's still too flaky to commit in its current state. * Remembered positions of dockable floating dialogs is inexact. For me (using Metacity), I'm not able to get the exact position of dockable floating dialogs, the values I get are off by an unpredictable number of pixels. Could be related to the problems described here: http://www.gtk.org/api/2.6/gtk/GtkWindow.html#gtk-window-get-position * Compiler warnings. Including GDL in the tree introduced a lot of compiler warnings. They're not serious, but it looks bad... Note that this change only applies to gtkmm:ified dialogs, i.e. dialogs that subclass UI::Dialog. I've gtkmm:ified "Fill & Stroke" and with this change, that version is now default. Dialogs left to be gtkmm:ified are the "XML Editor", "Tiled Clones", "Object Properties" (though it's about to be removed/replaced IIRC), "Text and Font". The "Find" dialog has been gtkmm:ified by Johan but is disabled by default as it needs testing (please help). Now let's hope I didn't break something important... ;) 1.https://sourceforge.net/tracker/?func=detail&atid=604308&aid=1688508&grou… 2.http://www.nabble.com/-PATCH--Dockable-dialogs%2C-and-some-concerns...-tf… -- Gustav

14 33