Batch Export confused by inkscape:export-filename

Please read the manual about (batch) exporting to bitmap: expprt hints are a feature, not a bug.

Possibly a duplicate of
Bug #411568 “Batch export should be more explicit about where it exports stuff”:
<https://bugs.launchpad.net/inkscape/+bug/411568>

Sorry, forgot to add the link to manual page:
<http://tavmjong.free.fr/INKSCAPE/MANUAL/html/File-Export.html#id4337007>

See also the release notes of Inkscape 0.46 about batch export and export hints:
<http://wiki.inkscape.org/wiki/index.php/Release_notes/0.46#Bitmap_export>

Expert hints is a good approach. But, currently they are a bit in conflict with usability as hints are set automatically without user interaction and later cause problems for the user not aware that they have been set. Maybe there could be a setting in the preferences for Normal/Expert Mode which decides if hints are to be respected or not? Or in this case, a check box in the Batch Export dialogue? Have I missed something if I claim that these hints are not accessible unless the user starts digging in to the XML?

Looks like a duplicate when it comes to consequences from a non expert user perspective.

Sorry if my original report sounded a bit harsh, was just trying to be short and clear.

> (…) hints are set automatically without user interaction (…)

If you close instead of save the file after exporting individual objects, the export hints do not get stored in the SVG file (i.e. after the last edit, save the file and only then export to bitmap, so that the latest changes - adding the export hints - can be discarded without losing any image data).

> Have I missed something if I claim that these hints are
> not accessible unless the user starts digging in to the
> XML?

The saved export hint is displayed in the 'Filename' field and can be edited in the dialog if the object is selected individually. There is no interface to globally reset or edit the stored export hints of all objects in the file.

> Sorry if my original report sounded a bit harsh

No problem ;)

Linking as duplicate to bug #411568 to keep tracking and discussion of the reported issue in one place. Please add a comment here and revert the duplicate status if you don't agree and think these are unrelated usability issues that need to be tracked and solved independently.