Bug 179002 - Place States in the Map - score incorrect
Summary: Place States in the Map - score incorrect
Status: RESOLVED WORKSFORME
Alias: None
Product: kgeography
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-28 23:05 UTC by geo
Modified: 2023-01-07 10:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
wrong result (35.83 KB, image/jpeg)
2008-12-28 23:07 UTC, geo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description geo 2008-12-28 23:05:14 UTC
Version:           0.5.9 (using KDE 4.1.3)
OS:                MS Windows
Installed from:    MS Windows

I believe that I answered the states correctly
Place States in the Map
1. select 8 states
2. do it correctly

it says I only got 1 out of 8 correct.
Comment 1 Albert Astals Cid 2008-12-28 23:07:25 UTC
Actually it's not a bug, just that:
a) the Place States in the Map is quite strict in what he considers a "right" answer
b) the summary view sucks for "Place States in the Map" mode

Suggestions welcome for both issues.
Comment 2 geo 2008-12-28 23:07:50 UTC
Created attachment 29709 [details]
wrong result
Comment 3 Laurent G. 2009-01-03 19:20:12 UTC
Hi.
For information the criteria between a good and a bad placing of a division is currently an usual (euclidian) distance --between where clicked was waited and where it occured finally-- not being more than 5 pixels long.
On Australia map, there is only one real difficulty : when Canberra is asked before New South Wales, because it the only case where you don't have any line (or any line that can be recognized easily enough) to ?lean? on. If you got a bad mark, it is because you played it loose on the placing ;-)
What could be done to make this part of the game more consistent and fair enough to placing skills ? My proposal is we should have a different answer dialog that don't show the color "Your answer" column but a column with some kind of distance and a boolean indication of whether this is good enough or not.
 What do you think about that solution ? What are yours ? Advice, even not complete, is welcome :)
PS: Nice to see that someone shows interest in playing with KGeography on Redmond OS too ;-)
Comment 4 Andrew Crouthamel 2018-11-02 04:18:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-16 02:43:17 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-07 00:23:59 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-22 05:19:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-06 05:23:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 9 geo 2023-01-07 10:07:37 UTC
Joseph gmail 

> On 6 Jan 2023, at 1:23 pm, Bug Janitor Service <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=179002
> 
> Bug Janitor Service <bug-janitor@kde.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|NEEDSINFO                   |RESOLVED
>         Resolution|WAITINGFORINFO              |WORKSFORME
> 
> --- Comment #8 from Bug Janitor Service <bug-janitor@kde.org> ---
> This bug has been in NEEDSINFO status with no change for at least
> 30 days. The bug is now closed as RESOLVED > WORKSFORME
> due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> Thank you for helping us make KDE software even better for everyone!
> 
> -- 
> You are receiving this mail because:
> You reported the bug.