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.

Sign up for GitHub

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

Jump to bottom

Starting a VM that no longer exists from an old shortcut results in an unhandled exception #36

Closed
daviunic opened this issue Dec 31, 2018 · 1 comment
Closed

Starting a VM that no longer exists from an old shortcut results in an unhandled exception #36

daviunic opened this issue Dec 31, 2018 · 1 comment
Assignees
@daviunic
Labels
bug Something isn't working

Comments

@daviunic
Copy link
Contributor

"Object reference not set to an instance of an object." Confirmed in 1.3.1, looks like I forgot to handle the case when the specified VM doesn't exist.
@daviunic daviunic added the bug Something isn't working label Dec 31, 2018
@daviunic daviunic self-assigned this Dec 31, 2018
daviunic added a commit that referenced this issue Dec 31, 2018
@daviunic
Fixed issue #36
ff566ea 
A proper error is now displayed when a non-existent VM is started via a shortcut.
Also changed the "VM already running" messagebox to information.
@daviunic
Copy link
Contributor Author

Fixed in 1.3.2.

notBald pushed a commit to notBald/Avalonia86 that referenced this issue Jan 7, 2025
@daviunic
Fixed issue 86Box#36
7a04a07 
A proper error is now displayed when a non-existent VM is started via a shortcut.
Also changed the "VM already running" messagebox to information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daviunic daviunic

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@daviunic