- Inkscape Devel - Inkscape Mailman

RE: [Inkscape-devel] "problem with gradients" (Bug 850924)
by bulia byak 10 Mar '04

10 Mar '04

>Summary: problem with gradients >Bug ID: 850924 I can't verify, but this bug is closed in sodi: http://sourceforge.net/tracker/index.php?func=detail&aid=782800&group_id=40… _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

Re: offset & simplify
by bulia byak 10 Mar '04

10 Mar '04

>to false). apparently illustrator does exactly the >same kind of errors in its offsets, so i suppose they >have taken the same method. You used a constant value in the call to Coalesce in sp-offset. I changed that to: SPItem *item = &(shape->item); NR::Rect bbox = sp_item_bbox_desktop (item); gdouble size = L2(bbox.dimensions()); gdouble exp = NR::expansion(NR::Matrix(item->transform)); if (exp != 0) size /= exp; orig->Coalesce (size * 0.001); I.e. I coalesce by the 0.001 of the item's size (divided by transform, because offset works with the original untransformed path). And it now works perfectly for most sizes! Only in the smallest size, at 256x zoom, there are noticeable distortions resembling pixelation, apparently because of a lack of precision somewhere causing nodes to "snap to grid". However, this is a much smaller annoyance than before. The version with my change is committed. Another change I did was reducing the minimum allowed radius from 0.25 to 0.01: if (fabs (offset->rad) < 0.01) offset->rad = (offset->rad < 0) ? -0.01 : 0.01; because with 0.25, there was a noticeable "jump" around 0 for small objects. _________________________________________________________________ Add photos to your e-mail with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

Re: offset & simplify
by bulia byak 10 Mar '04

10 Mar '04

>the offset quality is dependent on the simplification >quality, especially the "correct" version. for the >time being, i leave the bad version (selected by >setting the global use_slow_but_correct_offset_method >to false). apparently illustrator does exactly the >same kind of errors in its offsets, so i suppose they >have taken the same method. its advantage is that it's >faster, and easier to recombine in curves. but i still >haven't found a nice way to have a treshhold that >depend on the "detail" size (like for the "good" >version), so the simplification can eat some details. >as far as simplification is concerned, it's probably >wiser to leave someone else come up with a good >algorithm (and to not default to Coalesce(), which is >sometimes too strong). I tried use_slow_but_correct_offset_method = true, which gave good results indeed, but froze and crashed soon :( So I guess we should leave it at false for now. As for the current method, again, if it gives correct results for large objects, what prevents you from "tricking" it so it believes all objects are large enough for the artifacts to never appear? >also, when you say >"simplification", i assume you mean (a bit) >"smoothing". Yes, that's what is often needed in design, and what most people expect when they do "simplify": reduce the number of nodes making the path smoother. >The simplify() functions don't do >smoothing at all; they were intended to remove very >small segments in the path description, that's all. So I guess it's useful for doing simplification as part of the offset, but not usable for standalone Simplify command. >i can't remember what the defaults were for >yesterday's sp_selected_simplify(), but i don't think >i have done major changes to the behavior of simplify. >it's probably just the difference between >justCoalesce=true and justCoalesce=false Yes! options.simplifyjustcoalesce was 1 by default, now I changed it to 0 and it works very well again! With the starting threshold of 0.003 * size, it gives a very smooth transition from the original shape to the degenrate two-node path, preserving the original outline as good as it can on every step. Thanks, and please do not change the algorithm used by the standalone Simplify anymore! :) (you can of course tweak the algo used by offset, to fix the distortions, if this is possible at all) _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar � get it now! http://clk.atdmt.com/AVE/go/onm00200415ave/direct/01/

1 0

"problem with gradients" (Bug 850924)
by Bryce Harrington 10 Mar '04

10 Mar '04

Summary: problem with gradients Bug ID: 850924 ------------------------------------------------------------------------ If you use gradients in Sodipodi and then stretch the icon of the saved file in Nautilus, you'll notice, that the gradients are absolutly screwed up! Just try it yourself, draw a rect, give it a gradient fill, save it as svg or sodi-svg and do "Stretch Icon" with Nautilus... I assume there's something wrong with de definition of the gradients in the xml David ------------------------------------------------------------------------ Can anyone verify that this is a problem with how gradients are being stored in the SVG, or could it be a Nautilus problem? Bryce

1 0

offset & simplify
by bulia byak 10 Mar '04

10 Mar '04

Hi Fred, Your latest changes in the offset code are very promising. The offset behavior is now much better, it's almost perfect for most "normal" sizes and only breaks for really small objects. So I'm closing the "splotch" bug as no longer relevant, and to the "offset distortions" bug I attach a new sample file, sloam.svg, with three object sizes (one perfect, one slightly broken, one broken). As for Simplify, the best result I've seen from it was yesterday. Today (as of this writing) it behaves much worse: does not change anything until very high thresholds, and then suddenly distorts the shape beyond recognition. The nature of these distortions is similar to those in the broken (smallest) shape in sloam.svg. Obviously this is because offset uses the simplify command too. The behavior I want to see from Simplify is this: preserve the general outline of the path; allow to remove a varying number of nodes by varying the threshold; avoid distortions; behave consistenly and predictably for all threshold values. Yesterday's version was very close to that. Ca we return to it please? _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

shorcuts and keybindings for Adobe Illustrator, Macromedia Freehand and Jasc Web Draw
by Alan Horkan 10 Mar '04

10 Mar '04

For reference purposes I have collected lists of keybindings from other vector graphics applications (and because I think I remember Bulia saying if these lists were provided he would look into allowing different sets of shortcuts/keybindings.) I would have provided these last week but my laptop died so instead I have been forced to fix my CD burner and put these files on disk, I also have some Adobe Illustrator screenshots I will send as soon as I have time. Shortcuts for Adobe Illustrator CS http://www.maths.tcd.ie/~horkana/inkscape/illustrator/ (nice software but five hundred dollars?!? If they can do Adobe Photoshop Elements for ninety-nine dollars why haven't they done Adobe Illustrator Elements yet? The sooner cheaper and free alternatives take a bite out of their apple the better it will be for consumers. Adobe Illustrator Elements $99, my prediction for late 2005 early 2006). While I was at it I signed up for thier Beta testing program for the laugh but doubt they will ever ask me. Shortcuts for MacroMedia FreeHand MX http://www.maths.tcd.ie/~horkana/inkscape/WebDraw_Keyboard_Shortcuts.html (sorry about the lack of line wraps but if mozilla can wrap long lines when you view source I dont see why it doesn't do so when viewing text files). Shortcuts for Jasc Web Draw http://www.maths.tcd.ie/~horkana/inkscape/WebDraw_Keyboard_Shortcuts.html but I'm pretty sure for my playing with WebDraw that there are other undocumented keybindings. While I still have some time left on the evaluation periods for Macromedia Freehand MX and Adobe Illustrator are there any other things people would like me to check? Any bug reports or feature requests I should file to help move along the possibility of mulitple sets of keybindings/shortcuts? Hope this helps. Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/

1 0

RE: [Inkscape-devel] problems with win32 (German)
by bulia byak 10 Mar '04

10 Mar '04

>1. Fill does not work correctly. When I drag a rect filling is shown but >when I release the mouse the filling disapears. This is bug http://sourceforge.net/tracker/index.php?func=detail&aid=898753&group_id=93… Could you please attach a sample SVG with such disappeared rectangle to that bug. >2. Freehand tool works so far, but when I simplify that path the line is >scrumbled again (I say again, because this is the known problem in >environments where numbers does not have the english format) Yes, splivarot.cpp still uses printf. Can anyone please search the codebase and rewrite the remaining printfs, so we could finally close this bug? _________________________________________________________________ MSN Premium includes powerful parental controls and get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

Re: [Inkscape-devel] Virtual memory problems - win32
by bulia byak 10 Mar '04

10 Mar '04

>Build - 4 March >Load Keys file >1st load about 30 seconds after a "low virtual memory" message >2nd load 95s and machine hung when leaving page. > >Build - 5 March >1st load 27s >2nd load 68s >3rd load 3+minutes. The machine hung > >Repeat test of Build 1 March >1st load 11s >2nd load 9s >3rd load 9s >4th load 11s >prog exited cleanly. Which suggests it's not Mental's 7 March change after all, but something that happened between 1 and 4 March. Let's search CVS logs for those days. _________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

problems with win32 (German)
by Adib Taraben 10 Mar '04

10 Mar '04

Hi, I use the win32 build Inkscape0403090324.zip from Bob Jamisons Page. I have a german Win2k. 1. Fill does not work correctly. When I drag a rect filling is shown but when I release the mouse the filling disapears. 2. Freehand tool works so far, but when I simplify that path the line is scrumbled again (I say again, because this is the known problem in environments where numbers does not have the english format) HTH. Adib.

1 0

Re: [Inkscape-devel] Virtual memory problems - win32
by bulia byak 10 Mar '04

10 Mar '04

>Build - 7 March > >Inkscape crashes on first attempted load of Keys. Correct. That was the day when Mental did his big commit, and that day's Inkscape died on any SVG with text. _________________________________________________________________ MSN Premium helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1