Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InvalidArgumet=Value of '0' crash #89

Closed
anon8675309 opened this issue Dec 7, 2020 · 0 comments
Closed

InvalidArgumet=Value of '0' crash #89

anon8675309 opened this issue Dec 7, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@anon8675309
Copy link

Describe the bug
Clicking Start/Edit/Configure when a ROM is not selected results in an unhandled exception.

To Reproduce
Steps to reproduce the behavior:

  1. Start 86BoxManager
  2. Add a ROM
  3. Select the ROM
  4. Click Edit
  5. Click Apply
  6. Click OK, at this point you are back at the main screen and the buttons such as "Edit", "Start", and "Configure" are enabled, but no ROM is selected
  7. Click "Edit", "Start" or "Continue" button
  8. Observe unhandled exception error

Expected behavior
As a user, after editing a ROM, I would expect it to still be selected. Alternatively, I would expect all of the buttons which will not work when a ROM is not selected to be disabled.

Screenshots
crash

Environment (please complete the following information):

  • Host OS: WIndows 10 version 2004
  • 86Box 86Box-32-245af88d
  • 86Box Manager Version 1.7.2

Additional context
n/a

@anon8675309 anon8675309 added the bug Something isn't working label Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants