- Inkscape Devel - Inkscape Mailman

editing nodes
by Robert Crosbie 03 Dec '03

03 Dec '03

Here's a problem I noticed while editing nodes with the XML editor. Don't have time right now to submit a SF bug right now. Here's what I did: Draw a path Edited some points manually using XML dialog Moved different points using GUI The points I edited using XML dialog reverted back to their original values. Rob. http://members.rogers.com/rcrosbie _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

2 1

Minor bug
by Bob Jamison 02 Dec '03

02 Dec '03

Hi, all. I know that I should be using SF's bug machine, but it appears to be heavily overloaded at the moment. I just checked out the CVS trunk, and built it. It is -really- looking good. The current key bindings for selecting a drawing tool are wonderful. However, neglecting to release a key before its corresponding tool is used causes side effects. For example: Hold down the 'p', and start drawing using the freehand tool. You will get an error and a crash: ** ERROR **: file draw-context.c: line 1142 (spdc_add_freehand_point): assertion failed: (dc->npoints > 0) aborting... A suggested fix for this particular problem would be ultra simple. Repeated keystrokes are hitting this function, but any invocations after the first are being processed without giving them a new point. (Which seems proper). Instead of failing hard, fail soft: At draw-context.c line 1142, replace: g_assert (dc->npoints > 0); with if (dc->npoints < 1) return; This 'soft fail' seems to be indempotent, and I don't see any side effects. g_assert() is a bit harsh, anyway, IMHO. HOWEVER, this just fixes a particular symptom. The general case of repeating keys during a draw operation needs attention. Keep up the good work! Bob Jamison Titan Corp.

2 2

doxygen & manpage
by Kees Cook 02 Dec '03

02 Dec '03

tvon: can you correct the groups for the inkscape_web/doc/doxygen directories/files to be "inkscape", please? gouldtj: can you update your update.dox.sh to get the latest copy from inkscape_project? I added automatic manpage generation to it. -- Kees Cook @outflux.net

2 2

button size
by MenTaLguY 01 Dec '03

01 Dec '03

I made the tool selection buttons along the side larger than the buttons for various commands up top. While I'd experimented with this a while back and abandoned it, it's since been suggested a number of times (most recently by Jon), and Xara appears to do so as well, I decided to try it again. See what y'all think... -mental

3 2

I'm here, I swear
by Ted Gould 01 Dec '03

01 Dec '03

Hey guys, I just wanted to say that I'm not MIA, I was just gone over the holiday weekend (in the US it was Thanksgiving). I'm now catching up on the ~120 devel messages and ~180 CVS messages... I've already seen a couple for me to look at - I'll hopefully get through all tonight. --Ted

1 0

Fonts problem with win32 build
by Mael 01 Dec '03

01 Dec '03

Hello, Concerning the fonts problem in the win32 build (fonts are rendered in italic), I think this is because of the function nr_type_calculate_position in nr-type-directory.c which uses the name of the font and string comparisons to test if it contains "italic" "bold", etc .. But for example on my french win32 fonts are named with "italique" instead of "italic" and "gras" instead of "bold" and so on, so this function gives wrong results. Sodipodi_0_33_1_Setup_Win2000_XP.exe seems to have the same problem excepted that it finds normal as default style instead of italic (so it's less visible :), when I try to set the style of the font to "gras" or "italique" it always goes back to "normal". M

1 0

select within group
by bulia byak 01 Dec '03

01 Dec '03

I want to enable ctrl-click to select within group, but I don't see how it can be done. I've delved deep into the arena code and found that if a group is "transparent" then its members can be selected one by one. But how can I do that on ctrl-click? In select-context.c, the handler that checks what button/key was pressed seems to already get a selected item as an argument from the arena code. Will I have to analyze this preselected item on my own, or is there a more elegant way? Please enlighten me! -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0

Re: [Inkscape-devel] button size
by bulia byak 01 Dec '03

01 Dec '03

For now I would vote for: #define TOOL_BUTTON_SIZE 28 #define AUX_BUTTON_SIZE 22 but I think we need to try to add more stuff to the secondary toolbar to see how it will look. > Well, as it is the toolbar size forces the window to a fairly large > minimum height. I'm a little uncomfortable forcing a much larger > minimum size. We have a lot of room to grow :) Currently the default window is very small - 400x400 if without the toolbar strut. BTW maybe we should increase this a bit, say to 640x480. But ultimately the size and maximized state of the document window should be remembered from previous session. > Do you think it would be okay to permit the button bar to be cut off if > the window is resized smaller? I think the main toolbar should not be cut (and it's not likely to be cut anyway), but the secondary toolbar must be permitted to be cut off if the window is small. > Well, perhaps I should use the GTK detachable toolbar widget there, > though the plain GTK one is kind of weak. :/ What is wrong with it? Is there an alternative? Maybe in Gtkmm? It would be nice to have this done without coding it from scratch :) -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0

Warnings for unimplemented SVG styles
by Bryce Harrington 01 Dec '03

01 Dec '03

I've put in a change to the codebase for some warning messages. Previously, if Inkscape encountered style properties that were not implemented, it would issue a generic warning such as: Unimplemented style property id: 1042 I've created specific warnings for each feature, so now it will report: Unimplemented style property id SP_PROP_FONT_SIZE_ADJUST: value: -4 This won't affect the quantity of warnings issued, just their specificity. I figured as we strive to gain better SVG compliance, we'll want to know more precisely what features we're missing. The warnings are all in style.c. If you're interested in trying your hand at adding a new SVG style property, have a look-see there at the sp_style_merge_property function. Bryce

1 0

Re: [Inkscape-devel] button size
by bulia byak 01 Dec '03

01 Dec '03

Also, I think it makes sense to establish a certain difference in style between the primary and secondary buttons. The primaries may be more 3Dish, with shades and highlights; the primaries should be much simpler, with less colors, without any highlights or gradients. This contrast need not be too drastic, but still it may be helpful. Thus, from this viewpoint, the current node editor secondaries are OK, while for the selector, only the three last buttons (rotate and flip) are OK, others must be made simpler, flatter and more laconic. The same goes for zoom secondaries which are currently "too beautifil". -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0