mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-06 21:29:33 +00:00
[Request] Option in Check Dump to get info from previous submission info file and/or Redump for (some?) fields #862
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kokasgui on GitHub (Aug 24, 2025).
Originally assigned to: @mnadareski on GitHub.
Before You Submit
If none of those apply, then continue...
Is your feature request related to a problem? Please describe.
I'm a bit frustrated when I want to use Check Dump to add or change information on a given dump, because I always have to type everything again, making the information more prone to error when I feel I already know the information I'm typing
At the same time, another issue I have is, when cancelling the operation, all the info is gone, except for autofilled info from Redump
Describe the solution you'd like
Basically, every time a user starts a Check Dump procedure, the info is already filled with the previous submission info (except in the cases where there isn't, like when checking a PS3 CFW dump for the first time). Next to each field (at least for the most common ones, I don't know if it would be overwhelming to see it in every field) there would be a button to autofill/replace current text according to previous submission info file.
If the user had signed in with their Redump credentials and there was a Redump page match, there would be an extra button to copy the info from the Redump page at the user's will, instead of replacing everything in some of the fields
Describe alternatives you've considered
I thought of adding this button kinda like a checkbox in the fields, when checking it it would replace the field with the info taken from Redump and locking editing. However, it would be better if the user could edit that field from that point onwards, instead of locking it. Even still, it would be even better if the user could still get the info from the previous submission info file
Another idea I had which was way simpler was to just add an option in the Options menu to allow the user to either retrieve the info from Redump or from the previous submission file
Additional context
I hope that you could understand my problem from my explanation, even if it's not a big deal in the grand scheme of things. I think it could be a quality-of-life improvement to the usability of this operation and the software as a whole 🫶
@mnadareski commented on GitHub (Aug 24, 2025):
Duplicate of https://github.com/SabreTools/MPF/issues/844
@Kokasgui commented on GitHub (Aug 24, 2025):
Oh sorry, I hadn't found that suggestion before. Well, I hope the screenshot gives some idea how to implement in the UI 🤷♂️
@mnadareski commented on GitHub (Aug 24, 2025):
It currently does not read any information from existing submission info at all. What you're seeing is pulled information from the dump outputs and Redump, if there's a match. The issue is not a matter of dealing with it in the UI. The issue is how to handle it in the backend in a sane way.
@Kokasgui commented on GitHub (Aug 24, 2025):
Yeah I know, that will be the hardest part. I was just suggesting the UI implementation, but of course the backend retrieval is the main part needing a solution