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

Existing Bombing Damage Not Displayed on Bombing Target Selection Window #2333

Closed
ron-murhammer opened this issue Sep 7, 2017 · 4 comments
Closed
Labels
Problem A problem, bug, defect - something to fix

Comments

@ron-murhammer
Copy link
Member

ron-murhammer commented Sep 7, 2017

Bug: Bombing target selection window doesn't display existing bombing damage

Enhancement: Wanted to know if it would be possible to add a visual component to the target selection window for Bombing runs.

The current window appears as this:
image

However I was wondering if a visual component could be added like this:
image

The issue was brought to my attention that if you have multiple of the same target in the same territory one perhaps with damage and the other that does not... currently there is no way to tell them apart.

@ron-murhammer ron-murhammer added category: game engine > UI Problem A problem, bug, defect - something to fix labels Sep 7, 2017
@ron-murhammer ron-murhammer self-assigned this Sep 7, 2017
@DanVanAtta
Copy link
Member

Good catch, +1 to this suggestion.
@ron-murhammer should this be labelled as a usability problem instead as bug (aka defect)? A bug to me applies something is not working as intended or doing something very unexpected (and broken). This seems like a very good example of a usability problem to me, everything is working as intended, but in practice, the feature is difficult or impossible to use.

@ron-murhammer
Copy link
Member Author

@DanVanAtta It could go either way. Given that there is important information missing to make a decision, I'd lean towards bug in this case as we are not displaying something that absolutely should be displayed. Not really a big deal either way though.

@DanVanAtta
Copy link
Member

Instead of hijacking this issue further with bug vs usability, I opened a quick issue to discuss labelling: #2335, I only draw the nit distinction to justify having the two different labels, we perhaps may just want to merge the two labels.

@prastle
Copy link
Contributor

prastle commented Sep 8, 2017

Hepps drew a great diagram of what we talked about. I am curious about the overall decision. Either way it is definitely hard to understand if you are a first time user. Thus I definitely have to say its a usability issue. Is this a bug? hmm. I would say it is also a bug. Now that trains have been added we added one more thing that can be bombed to the item roster. Just my 2 cents @ron-murhammer @DanVanAtta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Problem A problem, bug, defect - something to fix
Projects
None yet
Development

No branches or pull requests

3 participants