[UserStory] Notify Users of an unrecognizable file type and let user select a new file

[ShayneKaiser]

User Story

Essential components

• Title describes the story
• Stakeholder type is identified
• Outcome is described
• Rationale is explicit
• Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a Imagelab user
I want to be notified that the type of the file I selected was not recognized by Imagelab and I am allowed to select a new file
so that I know why the file wasn't opened and I'm able to continue using Imagelab in the same instance.

Acceptance Criteria

• When a user selects a file type not recognized by Imagelab they are notified that the file type is not recognized by Imagelab
• After a user is notified that a file type was not recognized, the user is able to select a new file

Scenario 1

Given a user in Imagelab selects an image file by navigating to File > Open
when a file type not recognized by Imagelab is selected
then the user is notified that the file type is unrecognized and the user is able to select another file.

[JoeSGunter]

@ShayneKaiser @Codyhintzch @ColinLouis95 and myself trying to tackle this issue.

We believe the issue with the program seizing when an unrecognized file is selected is surrounding line 82 of the DisplayImage.java file and the while loops thereafter not having a case for a null pixel value.

[lonespartan12]

Allowing imagelab to accept all java compatible file is a good place to start. then throwing an exception after testing file type.

[jody]

throwing an exception

Because choosing a file of incompatible type is an expected behavior of the user, the suggested handling is by the program logic directly (rather than using the exception mechanism).

[JoeSGunter]

Unable to resolve this issue in time - we believe this problem is hand in hand with closing file dialog window seizing the program.

[CameronSpear]

@ThomasD0123 @CamiJolly1 @KaizenPool and myself are working on this issue
We are starting down a couple different paths to try and find the exact source of the issue and will comment further as we narrow in on the source of the problem and come up with a fix

[ThomasD0213]

Assign me too please!

[CamiJolly1]

me three!

[KaizenPool]

@ThomasD0123 @CamiJolly1 @KaizenPool and myself are working on this issue We are starting down a couple different paths to try and find the exact source of the issue and will comment further as we narrow in on the source of the problem and come up with a fix