pasted pixel images are stored in the wrong directory for new drawings

[Lars Kruse]

after creating a new inkscape document (without saving it for now), all pasted pixel images are immediately stored as files named "inkscape_pasted_image_???.???" in the directory where the last inkscape document was saved.
This is probably not what the user expects.

Additionally it is currently impossible to prevent the image files from being permanently stored, even if the user embeds the images into the document _before_ saving the document.

How to reproduce:
1) create a new document
2) paste a pixel image into this document
3) look for the new "inkscape_pasted_image_..." file in the directory where the latest document was stored

Instead I would expect the following:
When pasting an image into an unsaved document, the image file should be stored in a temporary directory.
As soon as the document gets saved somewhere, the image files are moved to that directory. This "move" operation is only necessary if the document was not saved/named before.

Alternative approach:
There could be a configurable directory location for storing pasted image files. If the directory is not defined, the current behaviour takes place.

thanks for your time!
Lars

[su_v (suv-lp)]

Are you still using Inkscape 0.47? Please add information about platform and inkscape version.

In the current stable release 0.48 pasted images are embedded and no longer create "inkscape_pasted_image_..." files.
<http://wiki.inkscape.org/wiki/index.php/Release_notes/0.48#Improved_bitmap_image_import>

[su_v (suv-lp)]

related:
Bug #170225 “relative image paths instead of absolute”:
<https://bugs.launchpad.net/inkscape/+bug/170225>

Bug #211607 “Crash when pasting raster image due to unwritable directory”:
<https://bugs.launchpad.net/inkscape/+bug/211607>

Bug #415374 “Only link bitmap images when user requests it”:
<https://bugs.launchpad.net/inkscape/+bug/415374>

Bug #555066 “Dialogue box Bitmap Copy”:
<https://bugs.launchpad.net/inkscape/+bug/555066>

[Lars Kruse (devel-sumpfralle)]

you are right - I am still using 0.47 on Debian (i386).

Thanks for the link to the release notes: this is a great improvement!
I guess, this bug can be closed now - sorry for wasting your time ...

[su_v (suv-lp)]

> this bug can be closed now

Closing as 'Fix released', setting milestone to 0.48.

> sorry for wasting your time ...

no problem :)