| Summary: | names of point objects don't follow the objects | ||
|---|---|---|---|
| Product: | [Applications] kig | Reporter: | Marco Clocchiatti <ziapannocchia> |
| Component: | general | Assignee: | Pino Toscano <pino> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Marco Clocchiatti
2005-05-29 11:22:44 UTC
Do you mean when moving Q1 too much to the left, overcoming Q2? If this is the case, the reason is a problem that I wanted to address some time ago, but it requires some work. Basically the motive for this is due to the fact that when intersecting a line and a circle kig always adds two new points, even if one is already present in the construction. The relative position of the two new points is not always what the user expects, when in moving mode. A way to fix this problem is for kig to understand cases when one of the intersections is already there and constructing only the other one. > Do you mean when moving Q1 too much to the left, overcoming Q2?
Yes, that's the problem.
I hope you may found a solution. I'm sorry, because I'ma not a programmer and I canno't help you.
For a now, I continue using kig in teaching, because it's a very good program.
Over all, I love python-scripting.
Allright, I have a patch for the problem, which you can find in http://dmf.unicatt.it/~paolini/kig/patches/otherintersection.diff It must be applied against the "branches/kig/post-kde-3.5/kig/" branch in the KDE svn repository. If all goes well the patch will be officially merged in the 'post-kde-3.5' branch and in the development version (kde4) If necessary I could also provide an rpm for a Fedora core 4 distribution, but that will require some time bear in mind that you cannot use the existen kig save file, but rather the construction must be redone from scratch, and will produce a different geometric construction (ConicLineOtherIntersectionType) note on the patch: at the moment only the conic-line intersection is addressed, subsequently also the circle-circle intersection will be patched similarly. 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! (In reply to Andrew Crouthamel from comment #4) > 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! I've just tested again the previous example, but the bug seems enduring again. probably, the patch by Maurizio Paolini was not applied. This may it be my fault, because I didn't replay him on 2006, and I'm sorry for this. Now, I think the old patch needs to be rewritten for the actual kig version. Anyway, I think this bug should remain as not solved. 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! (In reply to Justin Zobel from comment #6) > 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! Thank for your comment. A long time was elapsed since the initial report. But today, I tested again the file above, and the issue seems solved. thank's for your support. 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! 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! |