- Inkscape Devel - Inkscape Mailman

Icon sizes in Inkscape UI
by Michael Grosberg 18 Nov '07

18 Nov '07

Hi, I'm trying to create icons for Inkscape's Tango icon set. I noticed that while the icons in the current default set are designed as 16x16 pixel icons, they are rendered as 13X13 icons. I tried first to recreate the import and export icons. They look fine on the toolbar, but in the menu they don't look well at all. Strangely, the other icons look somewhat better. It almost looks as if the two icons I created are being rescaled using a "nearest neighbor" algorithm instead of interpolation. I checked and double checked - they are exactly on the grid and in the same size as the rest of the icons. So, I'd like to know, first, as long as this size is used, what should I do to make the icons look OK? Secondly, why was the 13X13 pixels size used in the first place? As far as I know Inkscape is the only app using this size. I also noticed odd icon sizes both in the SVG file (such as 27X27 icons) and on Ubuntu, some icons that should be small such as the four "affect" buttons at the end of the select and transform toolbar are excessively large. One more question I'd like to open for debate is, are too many icons used in the menus? Usually, only "important" features get icons, to make them more easily recognizable in a long menu. Giving everything an icon misses the point because easy recognition is no longer possible. We can still have all the icons in the icons.svg file, but I think the number of actually used icons in the menu should be lower.

4 5

new button
by bulia byak 17 Nov '07

17 Nov '07

Jon, what is that new button you added to the main UI? For me it's just disabled so I have no idea what it does. Judging by the code, it has something to do with "adjusting the display". Do you think this adjusting has to happen so often as to deserve a button right where you added it? I think any adjustments are best kept in preferences. In any case, the place you chose for the button is most unfortunate. I always hide the scrollbars to free some extra room for the canvas, and now this just results in two empty strips of unused space to the left and upwards from your button. In other words, your single button takes as much space as the two scrollbars! Please reconsider this. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 3

2Geom assertions => exceptions
by unknown＠example.com 17 Nov '07

17 Nov '07

Hi all, I've made a nice system to replace the 2geom assertions I think (this is what makes LPE crash in at least one case). Please have a look of what I coded into the 2geom dir of Inkscape now [1]. My next step is to change asserts into assert_invariants, such that an exception is thrown instead of a terminate(). I'd also like to splice the exception stuff from utils.h into a separate file. Planning on moving this to lib2geom svn head very soon; just give a shout when it's not any good! Cheers, Johan [1]: http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/2 geom/utils.h?revision=16507&view=markup

1 0

today's compile error
by bulia byak 16 Nov '07

16 Nov '07

main.cpp: In function 'void sp_do_export_png(SPDocument*)': main.cpp:981: error: 'errno' was not declared in this scope main.cpp:981: error: 'ERANGE' was not declared in this scope -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

2 1

Re: [Inkscape-devel] [Inkscape-user] Improved performance of the object snapper
by bulia byak 16 Nov '07

16 Nov '07

On Nov 16, 2007 12:04 PM, Diederik van Lierop <mail@...1689...> wrote: > bulia byak wrote: > > IMHO the key thing here is not just snapping to extensions of bbox, > > but _visualizing_ what it is that you snap to. In AI, it flashes the > > snap line when it snaps. We need to add infrastructure that would > > enable such displays when snapping, then smart guides will be easy. > > > > Absolutely! It's also needed for the post-snap visualization that was > discussed a few months ago, in which something lights up for a second at > the point that has snapped. What would be a good starting point in the > code to find out how such a thing would be drawn to the canvas? Do you > already have passive elements like that, not allowing user interaction > and disappearing after some time? Of course. We have a number of classes that draw various helper things on the canvas. These classes handle proper canvas redraw (so you don't have to worry about that) and usually have methods for setting coordinates, colors, showing/hiding etc. Note that unlike regular objects, these helper thingies can use inverse color so they are visible on any background. But these classes do not do any user interaction; that is performed by upstream classes that uses these display classes. They also have no provisions for automatically disappearing after a time, that you will need to add in your own code. Here they are: display/sp-ctrlline - draws a straight line, used by node tool bezier handles and by gradient tool for gradient lines display/sodipodi-ctrrect - draws an upright rectangle, used for rubberband selection display/sodipodi-ctrl - draws a number of various small fixed-size shapes, such as diamond, circle etc; used for knots and nodes display/sp-ctrlquadr - draws an arbitrary quadrilateral, used for text selection display/canvas-bpath - draws an arbitrary path with antialiasing, used for the red helper path in Node tool and for Pen tool, as well as for Tweak tool's circle (note: this one is slightly buggy, it leaves behind some dirt on the canvas; I want to switch it to using cairo but it's not yet possible due to incompatibility of buffer formats). You can search the codebase for a lot of examples of using these things. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

2 1

Re: [Inkscape-devel] [Inkscape-user] Improved performance of the object snapper
by unknown＠example.com 16 Nov '07

16 Nov '07

About the disappearing after some time: desktop->messageStack()->flash( Inkscape::WARNING_MESSAGE, "blah" ); That puts a message on the statusbar for a couple of seconds. -Johan > -----Original Message----- > From: inkscape-user-bounces(a)lists.sourceforge.net > [mailto:inkscape-user-bounces@lists.sourceforge.net] On > Behalf Of Diederik van Lierop > Sent: vrijdag 16 november 2007 18:05 > To: Inkscape User Community > Subject: Re: [Inkscape-user] [Inkscape-devel] Improved > performance of the object snapper > > bulia byak wrote: > > IMHO the key thing here is not just snapping to extensions of bbox, > > but _visualizing_ what it is that you snap to. In AI, it > flashes the > > snap line when it snaps. We need to add infrastructure that would > > enable such displays when snapping, then smart guides will be easy. > > > > Absolutely! It's also needed for the post-snap visualization > that was discussed a few months ago, in which something > lights up for a second at the point that has snapped. What > would be a good starting point in the code to find out how > such a thing would be drawn to the canvas? Do you already > have passive elements like that, not allowing user > interaction and disappearing after some time? > > Diederik > > > -------------------------------------------------------------- > ----------- > 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-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user >

1 0

SVN error
by Michael Yinger 16 Nov '07

16 Nov '07

Hi All, I'm trying to build an inkscape project by importing the inkscape SVN repository. Everything goes along fine until I get to xml-tree.cpp and I get an error. I've tried it with various SVN clients in Win XP and Linux (Fedora). I've been able to do this about a week ago. Can anyone explain what I'm doing wrong? Thanks for any help you can give. ... Added: C:\Documents and Settings\myinger\workspace\src\dialogs\item- properties.h Added: C:\Documents and Settings\myinger\workspace\src\dialogs\xml-tree.cpp Error: REPORT request failed on '/svnroot/inkscape/!svn/vcc/default' Error: REPORT of '/svnroot/inkscape/!svn/vcc/default': Could not read chunk delimiter: Secure connection truncated (https://inkscape.svn.sourceforge.net) Thanks. -- Mike

2 1

Re: [Inkscape-devel] perfect bound cover
by John Bintz 15 Nov '07

15 Nov '07

Alexandre Prokoudine wrote: > On Nov 9, 2007 2:44 PM, John Bintz <jcoswell@...1414...> wrote: >> That's because I didn't actually test to see if <_option> elements >> worked, I just assumed it would. :( I just put that fix into the >> extensions code and now it's working. Try it now. >> > > For some reason options do not show up as translated :-/ Unfortunately, I'm not seeing how you would make the translated option elements show up correctly, even after getting the <_option> tags working. :/ Aaron, Ted: do you have any insights? Thanks, John

3 6

Mouse Location
by Gail Carmichael 15 Nov '07

15 Nov '07

Hi all! I'm playing with a little accelerometer and I want to see how well I can get it to work in Inkscape so that it would replace the mouse. I was wondering if anyone could tell me where exactly the mouse location is read? I am literally going to plug code to read this accelerometer there instead. Clearly, this is not work that will be usable in Inkscape! Just for fun :) Thanks, Gail

6 8

Re: [Inkscape-devel] [Inkscape-user] Improved performance of the object snapper
by Alexandre Prokoudine 15 Nov '07

15 Nov '07

On Nov 15, 2007 10:35 PM, Diederik van Lierop wrote: > Alexandre Prokoudine wrote: > > I wonder if within current snapping framework the so called Smart > > Guides are possible. That is -- snapping without touching. > > This is new to me, but it looks like it simply aligns > vertically/horizontally to the boundingbox of objects at any distance, > am I correct? Yes, both BB and rotation center. > Such a thing is not supported by the current snapping > framework, but it shouldn't be too difficult to implement. Sounds like a dream :) > If implemented, it will need a key binding though to easily turn this > on/off because otherwise it will get annoying. Definitely! :) Alexandre

1 0