Remember to try the latest WIP build to see if the feature already exists.
Is it copy protection related? If so, report the issue here instead.
.NET 6.0 has known limitations, so make sure that what you're asking for isn't already in another build.
Check previous issues to see if any of those are related to what you're about to ask for.
If none of those apply, then continue...
Is your feature request related to a problem? Please describe.
When filling out ringcodes or similar information on verifications, often times, the ringcodes will be similar to those on the matching page, and it winds up being fastest for me to copy the ringcodes out of the page and modify them to match mine.
Describe the solution you'd like
If already using the -c commandline flag, the user could be able to supply another flag to pull information not already included. For variable information, since there's no objective "answer", it seems fastest to just pull the first non-empty field for each.
Describe alternatives you've considered
At the moment, I just do it manually.
Additional context
This has obvious concerns. For starters, it definitely should not be included functionality in the MPF UI. Beyond that, there's still obviously a potential issue of typos, etc, being copied and missed, even from users who are "careful", If this PR cannot be accepted, I understand.
Before You Submit
If none of those apply, then continue...
Is your feature request related to a problem? Please describe. When filling out ringcodes or similar information on verifications, often times, the ringcodes will be similar to those on the matching page, and it winds up being fastest for me to copy the ringcodes out of the page and modify them to match mine.
Describe the solution you'd like If already using the -c commandline flag, the user could be able to supply another flag to pull information not already included. For variable information, since there's no objective "answer", it seems fastest to just pull the first non-empty field for each.
Describe alternatives you've considered At the moment, I just do it manually.
Additional context This has obvious concerns. For starters, it definitely should not be included functionality in the MPF UI. Beyond that, there's still obviously a potential issue of typos, etc, being copied and missed, even from users who are "careful", If this PR cannot be accepted, I understand.