Bug 297482 - It is not clear whether a point will be created or an existing point will be used in various tools
Summary: It is not clear whether a point will be created or an existing point will be ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kig
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Pino Toscano
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-04 17:16 UTC by Antoine
Modified: 2023-02-09 03:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine 2012-04-04 17:16:04 UTC
Create two points, then select the midpoint tool.
When you hover the first point, it should be very clear what Kig is going to do: create a new point, or use the existing point under the cursor. Because the cursor is partly hiding what's beneath, you can't really tell. You are forcing the user to rely on a visual clue (Has the red point merged with the existing blue point ? ), when you could simply change the floating tooltip to something meaningful:
"Construct Midpoint of this point and Another one" is too generic. If Kig knows what is going to happen, he should change the text to tell it to te user.
Comment 1 Jacob Welsh 2014-01-27 16:10:08 UTC
Or change the color of the target object. That is, have existing objects be highlighted when the cursor is close enough to "snap" to them in a construction. Advantages: easy to distinguish which object will be used, such as when there are several points close to each other; no need to write modified tooltip strings for every object for every language.
Comment 2 Andrew Crouthamel 2018-11-11 04:30:28 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 3 Andrew Crouthamel 2018-11-21 04:38:02 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-10 01:52:24 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 5 Bug Janitor Service 2023-01-25 05:05: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 6 Bug Janitor Service 2023-02-09 03:53:50 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!