[Request] pre / post batch files #247

New Issue

claunia · 2026-01-29T16:12:45Z

claunia commented

2026-01-29 16:12:45 +00:00

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

Originally assigned to: @mnadareski on GitHub.

Is it possible to add an option that let you launch/call an external file after (and maybe before) the "start dumping" process ?

Example:
It could be useful to call a batch file that could be launched after the dump process, to make some tasks like making some compressed files (one for logs only, one with all the files, one with only .img, only .scm, etc.), deleting files after compression, moving them, etc.

You could also add this on DICUI but probably too many cases (zip, 7z, rar, etc. On windows, other Oses, etc.).

Originally created by @Madroms on GitHub (Oct 11, 2020). Originally assigned to: @mnadareski on GitHub. Is it possible to add an option that let you launch/call an external file after (and maybe before) the "start dumping" process ? Example: It could be useful to call a batch file that could be launched after the dump process, to make some tasks like making some compressed files (one for logs only, one with all the files, one with only .img, only .scm, etc.), deleting files after compression, moving them, etc. You could also add this on DICUI but probably too many cases (zip, 7z, rar, etc. On windows, other Oses, etc.).

claunia added the enhancement help wanted labels 2026-01-29 16:12:45 +00:00

claunia closed this issue

2026-01-29 16:12:45 +00:00

claunia commented

2026-01-29 16:12:46 +00:00

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

I'm going to leave this open, but I'm not going to implement this for the following reasons:

It's already bad enough that I have to wrap DIC and Aaru the way that I do. A more coupled approach is what I'd want instead, but I have to do it this way for now.
This same functionality can be achieved by using Check, since in one of the more recent releases, check gained the ability to specify a drive path for doing things like copy protect scan and additional information extraction. Having that sort of batch will give you way more flexibility than the UI.
The UI is supposed to be meant for "the most common case" scenarios. Specialty things like that should be handled elsewhere.

I am leaving this open if someone else is willing to put the time into making this feasible.

@mnadareski commented on GitHub (Oct 11, 2020): I'm going to leave this open, but I'm not going to implement this for the following reasons: - It's already bad enough that I have to wrap DIC and Aaru the way that I do. A more coupled approach is what I'd want instead, but I have to do it this way for now. - This same functionality can be achieved by using Check, since in one of the more recent releases, check gained the ability to specify a drive path for doing things like copy protect scan and additional information extraction. Having that sort of batch will give you way more flexibility than the UI. - The UI is supposed to be meant for "the most common case" scenarios. Specialty things like that should be handled elsewhere. I am leaving this open if someone else is willing to put the time into making this feasible.

claunia commented

2026-01-29 16:12:47 +00:00

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

I'm officially closing this. This didn't fit into the idea of DICUI when it was opened and it doesn't fit into the design philosophy of MPF now.

@mnadareski commented on GitHub (Oct 11, 2023): I'm officially closing this. This didn't fit into the idea of DICUI when it was opened and it doesn't fit into the design philosophy of MPF now.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#247