[Request] Output Filename = Output Directory when you change the Output filename #240

Closed
opened 2026-01-29 16:12:38 +00:00 by claunia · 3 comments
Owner

Originally created by @Madroms on GitHub (Oct 11, 2020).

Originally assigned to: @mnadareski on GitHub.

Default: when disc is inserted and scanned, output filename is chosen automatically by DICUI, then output directory is filed with "Default Output Path""output filename without extension". Great.

When you change the Output filename, Output directory is not updated accordingly. This is normal.
But could you add an option that also update automatically the Output directory according to the new Output filename given by the user ?
It is better to write something only once, instead of twice ;)

Originally created by @Madroms on GitHub (Oct 11, 2020). Originally assigned to: @mnadareski on GitHub. Default: when disc is inserted and scanned, output filename is chosen automatically by DICUI, then output directory is filed with "Default Output Path"\"output filename without extension". Great. When you change the Output filename, Output directory is not updated accordingly. This is normal. But could you add an option that also update automatically the Output directory according to the new Output filename given by the user ? It is better to write something only once, instead of twice ;)
claunia added the enhancementhelp wantedgood first issue labels 2026-01-29 16:12:38 +00:00
Author
Owner

@sadikyo commented on GitHub (Oct 11, 2020):

If you decide to add this, please do not make it default or automatic. I know myself and others have systems that don't use this structure.

@sadikyo commented on GitHub (Oct 11, 2020): If you decide to add this, please do not make it default or automatic. I know myself and others have systems that don't use this structure.
Author
Owner

@mnadareski commented on GitHub (Oct 12, 2020):

I'm going to say, this is slightly niche for my liking. The default output path is meant as just that: a reasonable default. If a user decides to change the name of the file, as sadikyo was saying, I'm not sure how many people would expect it to also automatically adjust the path. If this is something that someone else wants to work on as an option, I'll leave this here for them. It seems simple in practice, I just don't think it's a good fit.

@mnadareski commented on GitHub (Oct 12, 2020): I'm going to say, this is slightly niche for my liking. The default output path is meant as just that: a reasonable default. If a user decides to change the name of the file, as sadikyo was saying, I'm not sure how many people would expect it to also automatically adjust the path. *If* this is something that someone else wants to work on as an option, I'll leave this here for them. It seems simple in practice, I just don't think it's a good fit.
Author
Owner

@mnadareski commented on GitHub (Oct 11, 2023):

Due to the complexities of how paths are handled, especially with broader dumping program support, I am going to have to deny this feature request outright.

@mnadareski commented on GitHub (Oct 11, 2023): Due to the complexities of how paths are handled, especially with broader dumping program support, I am going to have to deny this feature request outright.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#240