Fred, I noticed you changed something in the simplify algorithm, and I just reworked the command itself. Now it:

- works with multiple selected objects

- preserves the z-order position of the objects

- preserves the parent (i.e. you can simplify within group)

I also changed the hard-coded threshold value of 1.0 that you had. Now that value is:

- taken from preferences (options.simplifythreshold)

- multiplied by the size of the simplified objects, so you get the same result if you scale the object

- accelerated when you call the command is quick sequence.

The last one is especially useful IMHO. You press Ctrl+L; some simplification happens, but not enough for you. Without acceleration, you're stuck; you may go to preferences and edit the threshold there but it's a major hassle. Now, you can simply keep pressing Ctrl+L quickly enough (faster than twice a second), and on each press, threshold is increased by 0.5 of the original value. If you call simplify again after some pause, the value is back to its prefs default.

As for the algorithm itself, with acceleration it works well enough in my testing, I can always drive a path to a one- or two-node degenerate path and get a good range of intermediate simplification degrees along the way. However, when I end up with a one-node degenerate path which is closed, that path tends to grow quickly and rotate if I try to simplify it more, which is kinda weird. Unclosed paths are OK, they get to a two-node bezier and stop there. Can you do something about this growth&rotation?

_________________________________________________________________ MSN Premium with Virus Guard and Firewall* from McAfee� Security : 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...