Wrong error message when system/type is unknown, but "start dump" is clicked #119

Closed
opened 2026-01-29 16:09:52 +00:00 by claunia · 1 comment
Owner

Originally created by @gingerbeardman on GitHub (Jun 17, 2019).

Originally assigned to: @mnadareski on GitHub.

Using latest AppVeyor build.

  • System == unknown
  • Type == unknown

Actual

  • If I scan for disks, start dumping button becomes enabled
  • If I press it, I get the error "a complete dump already exists"
  • But there was no existing dump

Expected

  • I would expect to get the error "system and disc type are not set"
  • Maybe "start dump" should not be enabled in this situation?

Screen
Screen shot 2019-06-17 at 20 56 18

Originally created by @gingerbeardman on GitHub (Jun 17, 2019). Originally assigned to: @mnadareski on GitHub. Using latest AppVeyor build. - System == unknown - Type == unknown Actual - If I scan for disks, start dumping button becomes enabled - If I press it, I get the error "a complete dump already exists" - But there was no existing dump Expected - I would expect to get the error "system and disc type are not set" - Maybe "start dump" should not be enabled in this situation? Screen ![Screen shot 2019-06-17 at 20 56 18](https://user-images.githubusercontent.com/49612/59632799-f7a27900-9142-11e9-8e18-db2ed6df772c.png)
claunia added the bug label 2026-01-29 16:09:52 +00:00
Author
Owner

@mnadareski commented on GitHub (Jun 17, 2019):

Made sure that the selected item is not NONE before re-enabling the button.

@mnadareski commented on GitHub (Jun 17, 2019): Made sure that the selected item is not NONE before re-enabling the button.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#119