Auto-fill name for exported file doesn't change when opening a different file. #37637

Closed
opened 2013-11-27 00:21:39 +01:00 by Justin Jensen · 12 comments

System Information
Windows 7 Ultimate 64-bit
nVidia GeForce 230m

Blender Version
Broken: Blender 2.69.0 r60995

Short description of error
The filename suggested by the Blender export dialog does not change to reflect the currently opened file.

Exact steps for others to reproduce the error

  • Open a .blend file and click File > Export > Wavefront (.obj)
  • Notice the filename that is suggested by Blender (same as the name of the currently open file with a different extension)
  • Click File > Open recent... > [another .blend file]
  • Click File > Export > Wavefront (.obj)
  • Notice the filename that is suggested. It will be the name of the previous file, not the currently opened file.
**System Information** Windows 7 Ultimate 64-bit nVidia GeForce 230m **Blender Version** Broken: Blender 2.69.0 r60995 **Short description of error** The filename suggested by the Blender export dialog does not change to reflect the currently opened file. **Exact steps for others to reproduce the error** * Open a .blend file and click File > Export > Wavefront (.obj) * Notice the filename that is suggested by Blender (same as the name of the currently open file with a different extension) * Click File > Open recent... > [another .blend file] * Click File > Export > Wavefront (.obj) * Notice the filename that is suggested. It will be the name of the previous file, not the currently opened file.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @JustinJensen

Added subscriber: @JustinJensen

#37647 was marked as duplicate of this issue

#37647 was marked as duplicate of this issue

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Whats happening is operator settings are stored for reuse, this can be handy - its nice if you export to a directory that you can export a second time without having to navigate to that path all over again.

We could clear all stored operator settings on file load or...

We could look for all operators matching EXPORT_*_OT_*and only clear the stored path strings, but this seems a bit arbitrary.

Whats happening is operator settings are stored for reuse, this can be handy - its nice if you export to a directory that you can export a second time without having to navigate to that path all over again. We could clear all stored operator settings on file load or... We could look for all operators matching `EXPORT_*_OT_*`and only clear the stored path strings, but this seems a bit arbitrary.

Added subscriber: @brecht

Added subscriber: @brecht

I think it's quite useful if tool settings and paths like this get preserved over file loads. Even if I'm opening a new .blend file there's a good chance I want to export to the same directory, though probably not with the same file name.

I can't think of a good solution here. You could have some extra property flag to indicate that it is remember but not across file loads but I'm not sure about that. I wouldn't really consider this a bug.

I think it's quite useful if tool settings and paths like this get preserved over file loads. Even if I'm opening a new .blend file there's a good chance I want to export to the same directory, though probably not with the same file name. I can't think of a good solution here. You could have some extra property flag to indicate that it is remember but not across file loads but I'm not sure about that. I wouldn't really consider this a bug.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2013-11-27 22:37:18 +01:00

Closing, I can see sometimes this is confusing - it can be handy too.

Closing, I can see sometimes this is confusing - it can be handy too.

Added subscriber: @maiChan

Added subscriber: @maiChan

◀ Merged tasks: #37647.

◀ Merged tasks: #37647.
Author

I agree that the directory where the exported file will end up should stay the same, however it doesn't make sense to keep the file name the same. The way it's currently set up, I have to change the name for each file so that the next export doesn't overwrite the previous one. If I wanted to export my model with a different name, I would gladly change it but keeping it the same adds an unnecessary step when exporting from a bunch of files.

I agree that the directory where the exported file will end up should stay the same, however it doesn't make sense to keep the file name the same. The way it's currently set up, I have to change the name for each file so that the next export doesn't overwrite the previous one. If I wanted to export my model with a different name, I would gladly change it but keeping it the same adds an unnecessary step when exporting from a bunch of files.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#37637
No description provided.