Initialise filename with object name, not blend file name #2
Comments
Road-hog123
changed the title
|
Thank you for your suggestion! I agree that it would accelerate that workflow, but I would encourage you to look into the Automation section in the documention for an alternative workflow for files with a lot of export operations. With a little setup, exporting many objects in sequence can become just a couple of clicks. If you have any feedback about the implementation and/or documention of the automation feature, I would welcome it - it may still be beneficial to many users to add features like this to accelerate laborious but programming-free workflows, even if they duplicate functionality available through custom Python scripts. |
|
Given there's interest in this feature from at least 3 people, I'm reopening this with a view to implement this change. |
Add an addon preferences panel that contains a single preference to use the active object's name as the initial filename instead of the blend file's name. The preference defaults to disabled, which maintains the existing behaviour that matches default exporters - when first invoked the export filepath is initialised to that of the blend file, with subsequent exports remembering the previous filepath. When the preference is enabled, the stem of the export filepath is set to the active object's name each time the exporter is invoked - the rest of the filepath behaves as before. Characters that are invalid in Windows filenames are removed on all systems, with a placeholder being used if the active object's name contains no valid characters. Closes #2
Add an addon preferences panel that contains a single preference to use the active object's name as the initial filename instead of the blend file's name. The preference defaults to disabled, which maintains the existing behaviour that matches default exporters - when first invoked the export filepath is initialised to that of the blend file, with subsequent exports remembering the previous filepath. When the preference is enabled, the stem of the export filepath is set to the active object's name each time the exporter is invoked - the rest of the filepath behaves as before. Characters that are invalid in Windows filenames are removed on all systems, with a placeholder being used if the active object's name contains no valid characters. Closes #2
A little suggestion: In exporting, get the blender name of the selected 3D object placed on filename textbox. It's a little feature that agilize the workflow exporting many objects in sequence.
The text was updated successfully, but these errors were encountered: