- Inkscape Devel - Inkscape Mailman

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

08 Dec '03

> See what y'all think... I think the size contrast may be a bit more pronounced. However, making secondary buttons smaller is bad, they're hardly visible already. Especially the raise/lower buttons are hard to decipher, they're too complex and dark, perhaps someone will have to redraw them eventually. The main toolbar buttons may be made a bit larger, IMHO. Also, can we rearrange the toolbars so that the corner is occupied by the secondary toolbar, not the primary? Rationale: secondary toolbar may ultimately need lots of space for all its controls, so every pixel counts. The primary, on the other hand, is unlikely to grow significantly. And if you do that, can you provide a bit of separation between the toolbars by moving the primary one to the bottom a little? Ultimately I would like to see in that interval a "handle" that will let me drag the toolbar e.g. to the right edge or make it floatable, but until then, let it be just a few pixels of empty space. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

6 7

RE: [Inkscape-devel] sodipodi diff
by bulia byak 08 Dec '03

08 Dec '03

The diff is uploaded to inkscape_web cvs module as /misc/diff33.diff _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

5 6

Inkscape 0.36-pre1
by Ted Gould 08 Dec '03

08 Dec '03

There are files on Sourceforge: http://sourceforge.net/project/showfiles.php?group_id=93438 This is aimed at being an incremental build up to the final release. All of the bugs that are in the roadmap are currently fixed, with some more in the tracker. If anyone has any bugs that restrict Inkscape from being usable - this is a good time to bring them up. Also, there is work on the release notes for 0.36. The last ones weren't very good, so this time we're planning ahead so they are reasonable. If you have contributed code or bug fixes or anything to Inkscape between 0.35 and 0.36 make sure your contribution is in the Release notes. We don't want anyone's contributions to be left out. Wiki page: http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes I'm very excited about the 0.36 release - I hope everyone gets a chance to try this build out so that we can make it even better. --Ted

1 0

[Fwd: Re: button.c]
by MenTaLguY 08 Dec '03

08 Dec '03

Has anyone else had difficulty building button.c since I made this change? -----Forwarded Message----- From: MenTaLguY <mental@...3...> To: bulia byak <archiver_1@...19...> Subject: Re: button.c Date: Sun, 07 Dec 2003 19:07:50 -0500 On Sun, 2003-12-07 at 02:32, bulia byak wrote: > Mental, your latest button.c only compiles if I change > > g_signal_handlers_block_by_func (G_OBJECT (button), G_CALLBACK > (sp_button_perform_action), NULL); > gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON (button), down); > g_signal_handlers_unblock_by_func (G_OBJECT (button), G_CALLBACK > (sp_button_perform_action), NULL); > > by > > g_signal_handlers_block_by_func (G_OBJECT (button), (void*) G_CALLBACK > (sp_button_perform_action), NULL); > gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON (button), down); > g_signal_handlers_unblock_by_func (G_OBJECT (button), (void*) G_CALLBACK > (sp_button_perform_action), NULL); > > Is that the right fix? No. Casting a function pointer to a normal pointer isn't safe or portable -- you can get away with it on x86, but on many architectures (like e.g. Itanium), a function pointer is really a much larger "function descriptor" datatype. Actually, this should compile as-is (it did compile for me), so it's something funky with one of our build configurations (not sure whose yet). I'm using gcc 3.3.2 with CFLAGS="-g -Wall", and building with glib 2.2.3. What compiler, compiler options, and version of GLib are you using, and what error(s) do you get when you try to compile? -mental

3 5

Ruler issues
by Michael D. Seymour 08 Dec '03

08 Dec '03

This will get submitted as a bug, but I believe it warrants discussion. 1) It seems the ruler co-ordiante system is flipped in the y-axis w.r.t. the SVG co-ordinate system. The rulers have their origin on the bottom left of the given viewport, and the co-ordinates increase up and to the right. This goes against the SVG spec, which states that the origin of the viewport is on the top left, and co-ordinates increase to the right and down. When creating a rectangle and manually specifying the (x,y) = (0,0), the top left corner is placed at the top left of the viewport. Odd that nobody noticed this earlier. 2) The markings used in the ruler gradations aren't anti-aliased. It looks like Inkscape uses some sort of customized GTK ruler. One should note that the GTKRuler class is being moved out of GTK+ because it's too specialized/little-used. One would think that just about any drawing/display app needing co-ordinates in its display canvas would use them. -- Michael D. Seymour "Data is not the plural of anecdote" tel: (416) 545-1060 -- Robert L. Park e-mail: michael_d_seymour@...93... web: http://www.astro.queensu.ca/~seymour/

1 0

Re: [Inkscape-devel] docked toolbar steals focus
by bulia byak 08 Dec '03

08 Dec '03

>Ick. > >To be honest I still don't totally understand how events are handed off >to event contexts in Sodipodi/Inkscape. :/ Neither do I. But you have much better overall knowledge of the program's innards. I start to feel that this problem is not for me :( I'll keep poking but... _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjo…

1 0

Re: [Inkscape-devel] [Fwd: Re: button.c]
by bulia byak 08 Dec '03

08 Dec '03

>On Sun, 7 Dec 2003, MenTaLguY wrote: > > Has anyone else had difficulty building button.c since I made this > > change? Here's what I see: button.c: In function `void sp_button_toggle_set_down(SPButton*, int)': button.c:189: error: invalid conversion from `void (*)()' to `void*' button.c:191: error: invalid conversion from `void (*)()' to `void*' $ gcc -v Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.1/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++,ada,f77,objc,java,pascal --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk) Glib is 2.3.2 as far as I can see. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

node edit news
by bulia byak 08 Dec '03

08 Dec '03

(Sorry if this comes in several copies, I'm having trouble sending to the list) I just did a temporary hack: now sp_document_undo emits the selection_changed signal. The node editor catches it and redraws the path. This fixes bug 848355 for now. As an unwanted side effect, selected nodes are deselected after an undo. A better solution would require figuring out what's up with selection_modified signal and using it instead (see my previous mail - attached below). On the bright side, today I implemented duplicate node in node editor (shift-d). As a regular duplicate object (ctrl-d), it places the new node(s) exactly over the previously selected ones (and selects the new node(s) instead). By using together with Tab and Ctrl-a, this makes possible some nice keyboard-only effects. Here are some ideas for eyecandy screenshots for 0.36: - create a filled star with about 30 rays, press ctrl-shift-c, F2, ctrl-a, shift-d, some arrow keys (maybe with shift).... - create a spiral with about 30 revolutions, ctrl-shift-c, F2, ctrl-a, shift-d, some arrow keys... Also, I fixed shift-b (break nodes) so that it breaks all selected nodes and only selects one end of each break (previously it selected both ends). So you can add more fun to the above examples by pressing shift-b, some arrow keys, then ctrl-a again, shift-d, more arrow keys, etc. More usefully, this allows to easily "draw" with keyboard. Use tab to move to the end node of an unclosed path and go like this: shift-d, arrows, shift-d, more arrows, etc. It's an easy way to create rectangular shapes, very useful for diagrams. So what remains in node editor is implementing the []<> keys to edit control points, and voila - a totally keyboard-driven path editor! Something I've dreamed about for long, but did not see to date in any vector editor. P.S. Looks like my previous mail was lost, here it goes: Does anyone have an idea why sp_selection_idle_handler in selection.c is constantly emitting the "selection modified" signal - even two signals, one on the selection and the other on the inkscape object??? There is indeed a constant flood of these signals even when absolutely nothing is happening, not even a mouse move. Is this by design? I'm sure there must be a better way. I was investigating why undo and XML-editor changes in node edit do not work, and found that nodepath context lacks any callback that would update the path when its repr has changed. I tried to hook it up to the "modified" signal but that rendered the program unusable because that signal is "always on" like white noise. Can someone share any insights? It seems to me that something is seriously broken here. I think that it's the repr subsystem that must issue a signal when the document is changed, but that subsystem apparently emits no signals whatsoever. _________________________________________________________________ Don�t worry if your Inbox will max out while you are enjoying the holidays. Get MSN Extra Storage! http://join.msn.com/?PAGE=features/es

3 3

Re: [Inkscape-devel] docked toolbar steals focus
by bulia byak 08 Dec '03

08 Dec '03

> > >Grabbing focus between widgets is accomplished via > > >gtk_widget_grab_focus(). The widget will need to have the >GTK_CAN_FOCUS > > >flag set, however. (we should probably do this for the canvas) > > > > OK, I'll investigate the grabs mechanism. Maybe if the fix is simple it >will > > go into this version. > >I've taken care of the latter half in desktop.c now (setting the >CAN_FOCUS widget flag). > >I guess what remains is just determining when it would be appropriate to >call gtk_widget_grab_focus() on the canvas widget. I cannot make it work. I added gtk_widget_grab_focus (&(dtw->canvas->widget)); into sp_desktop_widget_new in desktop.c. For debugging, I also added gtk_signal_connect (GTK_OBJECT (&(dtw->canvas->widget)), "event", GTK_SIGNAL_FUNC (sp_canvas_event_handler), &(dtw->canvas->widget)); and put some debug output into sp_canvas_event_handler. With or without the grab, it looks like the canvas widget gets keypresses, but does not pass them on to the event context. That is, it does pass it to the event context but only when the mouse is within the canvas. Maybe we need to grab focus on the event context, not on the canvas? But how to do that? I think the event context is not a GTK widget. _________________________________________________________________ Shop online for kids� toys by age group, price range, and toy category at MSN Shopping. No waiting for a clerk to help you! http://shopping.msn.com

2 2

RE: [Inkscape-devel] Gtk Buttons
by bulia byak 07 Dec '03

07 Dec '03

Also a question: if we want to restore the drop-down button lists for some tools, as were used for e.g. shape tools in SP, can we do that with the standard widget? >From: MenTaLguY <mental@...3...> >To: Inkscape ML <inkscape-devel(a)lists.sourceforge.net> >Subject: [Inkscape-devel] Gtk Buttons >Date: Sat, 06 Dec 2003 01:30:33 -0500 > >It turns out that SPIcons weren't equipped to deal gracefully with >situations where they were allocated less space than they were >requested. I fixed this, as well as adjusting the buttons' requested >size slightly. > >While I was mucking around in there, I also removed the code that drew >random garbage in icons that weren't present (it turns out to have been >a deliberate decision in Sodipodi). > >Anyway, CVS HEAD now has standard Gtk buttons. > >-mental ><< signature.asc >> _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

4 3

docs/keybindings.txt
by bulia byak 07 Dec '03

07 Dec '03

That file is old. Can we set it up so that it's automatically updated from the KeyboardShortcuts wiki page? It's where I keep all shortcuts up-to-date, and it's much better categorized too. _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

RE: [Inkscape-devel] Marker screenshots
by bulia byak 07 Dec '03

07 Dec '03

>I put a screenshot and example svg of path arrowheads / markers on the >website... Markers are good, but have you seen my message "node edit news" with screenshots suggestions? I'd like to see them implemented instead of the second screenshot with stars. Sodipodi can do stars, too - but we need to show something only we can do :) _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

button.c
by bulia byak 07 Dec '03

07 Dec '03

Mental, your latest button.c only compiles if I change g_signal_handlers_block_by_func (G_OBJECT (button), G_CALLBACK (sp_button_perform_action), NULL); gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON (button), down); g_signal_handlers_unblock_by_func (G_OBJECT (button), G_CALLBACK (sp_button_perform_action), NULL); by g_signal_handlers_block_by_func (G_OBJECT (button), (void*) G_CALLBACK (sp_button_perform_action), NULL); gtk_toggle_button_set_active (GTK_TOGGLE_BUTTON (button), down); g_signal_handlers_unblock_by_func (G_OBJECT (button), (void*) G_CALLBACK (sp_button_perform_action), NULL); Is that the right fix? _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

Marker screenshots
by Bryce Harrington 07 Dec '03

07 Dec '03

I put a screenshot and example svg of path arrowheads / markers on the website... http://www.inkscape.org/screenshots/ Bryce

1 0

[Fwd: [Sodipodi-list] [Fwd: Sodipodi bug 758775]]
by MenTaLguY 07 Dec '03

07 Dec '03

-----Forwarded Message----- From: John Stracke <francis+keyword+sodipodi.6389c0@...99...> To: Sodipodi <sodipodi-list(a)lists.sourceforge.net> Subject: [Sodipodi-list] [Fwd: Sodipodi bug 758775] Date: Sat, 06 Dec 2003 12:00:29 -0500 (I sent this to Lauris at first, but maybe he's been too busy with the 0.33 release. Anybody else have commit access?) I've just uploaded a patch for sodipodi bug #758775 (the one about export bounding box not considering stroke width). It's not complete (it doesn't do text, and it's overeager--it takes the view that it's better to err in the direction of including extra blank space than to cut off some of the diagram), but I believe it's solid enough and useful enough to check in. https://sourceforge.net/tracker/?func=detail&atid=104054&aid=758775&group_i…

1 0

RE: [Inkscape-devel] Bug priorities
by bulia byak 07 Dec '03

07 Dec '03

850971: dupe of 840375 _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjo…

2 1

[Fwd: [Sodipodi-list] [Fwd: Sodipodi bug 758775]]
by Jonathan Phillips 06 Dec '03

06 Dec '03

we have this problem too...its in our bug tracker... any takers... jon -----Forwarded Message----- From: John Stracke <francis+keyword+sodipodi.6389c0@...99...> To: Sodipodi <sodipodi-list(a)lists.sourceforge.net> Subject: [Sodipodi-list] [Fwd: Sodipodi bug 758775] Date: Sat, 06 Dec 2003 12:00:29 -0500 (I sent this to Lauris at first, but maybe he's been too busy with the 0.33 release. Anybody else have commit access?) I've just uploaded a patch for sodipodi bug #758775 (the one about export bounding box not considering stroke width). It's not complete (it doesn't do text, and it's overeager--it takes the view that it's better to err in the direction of including extra blank space than to cut off some of the diagram), but I believe it's solid enough and useful enough to check in. https://sourceforge.net/tracker/?func=detail&atid=104054&aid=758775&group_i… -- Jonathan Phillips <jon@...15...>

4 4

RE: [Inkscape-devel] Bug priorities
by bulia byak 06 Dec '03

06 Dec '03

842565 - fixed, please test and close bug 846963 - I think is fixed too 848355 - fixed temporarily, a better fix needs more work, but the bug may be closed because 852973 stays, and the better fix will have to fix them both 842564 - I would mark this "feature not a bug" 843123 - fixed 848694 - again feature not a bug, a discussion is on wiki (see CurrentColorWidget) 842627 - I cannot reproduce, anyone else? 853858 - this is what we discussed recently about copying <defs>, I think it's unlikely to be fixed before the release _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

2 1

Re: [Inkscape-devel] docked toolbar steals focus
by bulia byak 06 Dec '03

06 Dec '03

> > So the toolbar steals focus and won't let it go no matter how you try. >Since > > this involves moving focus not between windows but between widgets, I'm >not > > sure how to address this. > >Well, this basically arises as the buttons (by default) are set up to >accept keyboard focus on click, but the canvas widget is not. > >The toolbar buttons should probably not accept keyboard focus, though, >as they (almost) all have keyboard shortcuts anyway. I have fixed that >much in CVS. Yes, this problem is gone today - thanks a lot! >Grabbing focus between widgets is accomplished via >gtk_widget_grab_focus(). The widget will need to have the GTK_CAN_FOCUS >flag set, however. (we should probably do this for the canvas) OK, I'll investigate the grabs mechanism. Maybe if the fix is simple it will go into this version. http://sourceforge.net/tracker/index.php?func=detail&aid=854425&group_id=93… > > > > (see my comment at bottom). Basically we need all buttons to give focus >to > > the canvas at once, and all text fields must do the same on esc or enter > > (and not grab focus until you explicitly click on them). > >Well, in the case of dialogs we at least want basic standard navigation >keys like e.g. tab to advance focus to work, as well as accomodate any >IMs that might be active. With dialogs, keyboard focus now works more or less as it should: you can keyboard-navigate within a dialog, and Enter or Esc leave it. When we'll have spinbuttons and textfields in the aux toolbar, we'll need to make sure they behave consistently (tab for moving between widgets, esc to send focus to canvas, enter to set the value and send focus to canvas) and never grab focus unless clicked (or unless activated by a shortcut). As for shortcuts, I propose this: - all top-level menus must have hot-keys and be activated by alt-hotkey, e.g. alt-f must open the File menu - all text labels next to spinbuttons and textfields in the aux toolbars must also have hotkeys (underscored letters), and: -- either we make sure that these hotkeys never clash with the top menu hotkeys, and both are called by alt-hotkey -- or we can use independent hotkeys for the aux toolbar and use a different modifier (e.g. alt-shift-hotkey) for them Ideas? _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

Inkscape website above soft quota
by Bryce Harrington 06 Dec '03

06 Dec '03

There is a 100M soft-limit for project files on SourceForge. We're at 124M. 3.4M backup 0 cgi-bin 0 htdocs 9.1M inkscape 544K inkscape_project 106M inkscape_web 296K wiki 4.1M wiki_db 19M inkscape_web/cvs-snap 40M inkscape_web/doc 40M inkscape_web/doxygen 3.3M inkscape_web/inkscape_web 1.8M inkscape_web/magnethead 2.3M inkscape_web/screenshots Perhaps the doxygen files could be trimmed down? Or else maybe we should consider hosting them from another location? Bryce

1 0

Re: [Inkscape-devel] a few bugs I need tested...
by bulia byak 06 Dec '03

06 Dec '03

>I think I tend to prefer having the feature requests end up in Wiki, >since that allows them to be elaborated on, discussed, revised, >etc. which is valuable to do in order to make them implementable, and >that's exactly the sort of thing Wiki's are good for. The RFE tracker >works good as an "inbox" since it gives a consistent way for users to >submit to, along with bugs and patches. I think any small and unconnected requests may go to the tracker, but any larger requests that need discussion, or groups or interrelated requests, must be on wiki under "New features discussion" (hierarchized and categorized if possible). _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjoin…

1 0

Bug priorities
by Bryce Harrington 06 Dec '03

06 Dec '03

I've gone through the non-prioritized bugs in the SF bug tracker and assigned them priorities of 9, 6, or 3. We should not release until all priority 9 bugs are resolved. We should also seek to close as many of the priority 6 bugs as we can within the time available. Priority 3 bugs can be left until after the release, although many will be quick fixes and would be nice to get resolved. I've assigned a few bugs to people, and would encourage everyone to look through the list for ones they know how to fix, and take them if they're not taken already. There are seven priority 9 bugs, none of which have owners yet. Most have to do with saving/opening, and thus can impact user confidence a great deal. Many of the priority 6 bugs are crashes, and are thus important for that reason, even if they occur infrequently. Bryce

1 0

a few bugs I need tested...
by Jonathan Phillips 06 Dec '03

06 Dec '03

Hello, Well, I've finished transferring as many bugs that still have problem in the most recent build of inkscape-20031203, to the inkscape bug tracker on sf.net. There are still a few I need help with either because I do not know how to test them, or they require win32/mac os X. The ones to check from http://sf.net/projects/sodipodi bug tracker: #642384 Misrendered file -- text not aligned #834520 Crash when using a huge R1/R2 value for star shape #830980 LandScape Printing #768804 Sodi doesn't refresh font list; crashes reading deleted font #751439 UTF8 in font names creates problems Please report back to me which one you looked at and the outcome because I'm trying to keep track of the transfer with a spreadsheet. Also, if the bug still exists, please post the outcome on the bug tracker. Thanks, and after these 5 are looked into, the transfer of bugs is complete. Then we need to hack on them ;) Thanks, Jon -- Jonathan Phillips <jon@...15...>

2 3

Re: [Inkscape-devel] [Fwd: [Sodipodi-list] [Fwd: Sodipodi bug 758775]]
by bulia byak 06 Dec '03

06 Dec '03

> > It's actually not as simple as just taking the stroke width into > > account, either -- when you have mitred corners, they can stick out FAR > > beyond the stroke width. > >Markers too. > > > SVG filters will also make finding the real bounding box increasingly > > interesting, when we implement them. Maybe the renderer subsystem can give us the true bounding box of an object? I think this would make sense. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

RE: [Inkscape-devel] rotate/scale transformation crash
by bulia byak 06 Dec '03

06 Dec '03

>Draw a line/curve >Bring up transform dialog >Enter a value to rotate or scale >Apply >Apply again. > >This causes a segfault for me. Anyone else? Works for me, no segfault _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjo…

2 1