Quick Setup: Do not change ‘Minimum memory’ based on ‘Maximum memory’ field

[brawaru]

Operating System

Windows, macOS, Linux, Other

Version of Prism Launcher

Prism Launcher 5.1

Version of Qt

Qt 6.4.0

Description of bug

When entering into the field ‘Maximum memory allocation’ a number less than the number in ‘Minimum memory allocation’, the number in ‘Minimum memory allocation’ automatically updates to the number in ‘Maximum memory allocation’, creating frustrating experience where you have to go back and change value in ‘Minimum memory allocation’ again.

Would be better if this updating behaviour would only happen when ‘Maximum memory allocation’ field lost focus. Ideally, however, it should not happen at all, instead showing an error when user clicks the ‘Finish’ button that their ‘Maximum memory allocation’ is less than value in ‘Minimum memory allocation’, forcing them to notice and manually fix the mistake. The reason for the error rather than guess work is because this may slip through unnoticed, especially if the user relies on assistive technologies like screen reader that won't announce that ‘Minimum memory allocation’ value has been automatically updated.

Steps to reproduce

1. Remove launcher configuration / start fresh installation to force quick setup to show.
2. Select your language to proceed to problematic step.
3. On Java step enter ‘256 (MiB)’ in ‘Minimum memory allocation’.
4. Select everything in ‘Maximum memory allocation’ field and start entering ‘2048 (MiB)’ one digit at a time.

Observe as you enter the digit 4, that the value in field ‘Minimum memory allocation’ changes to match what's currently entered in ‘Maximum memory allocation’ field, thus to ‘204 (MiB)’.

Suspected cause

Poor design decisions.

This issue is unique

• I have searched the issue tracker and did not find an issue describing my bug.

[brawaru]

Thank you legend @Trial97!