Make a Bitmap Copy should embed

am looking at trying to fix this by using internal pixbufs and embedding the image rather than pointing at a tmp file.
Have the rendering to pixbuf done, just need to work out the base64 encoding.

Maybe a warning if the svg file isn't saved would avoid this problem.
Another warning when deleting a created bitmap copy letting you choose if you want erase the file or keep it would be useful.

the directory where it is saved is now the document directory; if doc is unsaved, your home dir.

"bad reference" is fixed.

John, if you can finish the embedding thing that would be great, for now I'm lowering the precedence.

Fixed in 9144 - the bitmap copy is always embedded now.

I think there should be a dialogue box giving the option to embed or not, as done by importing an image. And along with the option to link the location to save the bitmap.
I suggest doing this because there are people who take advantage of this "bug" how to edit it externally.

Sorry for English.

Frank: yes, there is a dialog that gives you the choice between linking and embedding. The dialog is not shown when you are pasting pixel data or making bitmap copies - in this case images are always embedded, because there is no file to link to.

But exactly what I'm saying this, should have the option. I think the user should choose between embedding or not the Bitmap copy or pasted. The bitmap generated can be located in the same directory with the svg file or another which the user chooses.

Thanks for the reply.
Sorry for English

In a complex art, for example, consists of several bitmaps. Now, the way it is, I think I miss the convenience of treating them or edit them externally in order to obtain a setting more specific. Own experience and the experiences of many other users of Inkscape, this is not the only goal. Use often in the development of websites layouts, backgrounds where I create and edit based on Gimp. Now the way to do this has become more arduous and long.

Sorry for the double reply, and my English.

Use the Extract Image extension (Extensions->Images->Extract Image). It will allow you to pick a sensible path for the linked image. This is better than automatically generating a crazy name.

Well, better than a crazy name, when needed this should just generate a deterministic name. There should be an option to allow for this. Yes, embedding solves it the issue for many people, but then it causes problems for others.

"Extract Image" is better, because it allows the user to pick a sensible name. It's impossible to guess how the user wants to call the linked file - let's allow him to tell us.

The currently available extension 'Extract Image…' does not allow the user to *pick* a sensible _path_ nor offer any visual control/feedback about the location of the extracted image (see bug #554734). IMHO 'extract image(s)' needs to be handled internally, not as a script extension (which doesn't have access to the file chooser nor knows about the location of the SVG file the image is extracted from), even more so when not offering the choice to link or embed pasted/bitmap-copied images.

Jon Cruz, I created a new bug continuing to bug 169108, since that particular bug is resolved.

Thanks

Sorry for English

Bug 555066