![](https://secure.gravatar.com/avatar/284c330bbc0d5070b1bb10e298c9ff6a.jpg?s=120&d=mm&r=g)
On Thu, 10 Jul 2008 11:29:08 -0700 "Quentin Hartman" <qhartman@...155...> wrote:
On Thu, Jul 10, 2008 at 11:17 AM, john cliff <john.cliff@...155...> wrote:
Is it in an area with gradients at all? sounds like an id clash between the gradients in the different files meaning the wrong ones getting referenced.
That's almost certainly it. I was approaching this conclusion after doing some more troubleshooting. Any ideas for an automatable way to make sure the gradient IDs are different amongst all my source files? I'm thinking some sort of script that digs into the SVG source would be about the only good answer. A nice feature for a future version of Inkscape would be checking for and warning on collisions like that, ideally with a few options for handling them.
Perhaps Inkscape should distinguish between user IDs it should not change (even if that causes problems like Quentin's seeing) and Inkscape generated IDs it's free to alter to avoid clashes.
Sometimes users are going to have IDs in a file to tag targets they want to manipulate outside Inkscape, and Inkscape shouldn't munge them.
IDs it's safe to change could be marked many ways, they could start with "i.", or end in [0-9] (which is currently the case?).
Cheers -Terry