Bug 106440 - names of point objects don't follow the objects
Summary: names of point objects don't follow the objects
Status: RESOLVED WORKSFORME
Alias: None
Product: kig
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Pino Toscano
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-29 11:22 UTC by Marco Clocchiatti
Modified: 2023-01-03 05:28 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Clocchiatti 2005-05-29 11:22:44 UTC 
Version:           Qt: 3.3.4
KDE: 3.4.0
Kig: v0.10 (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages0
Compiler:          gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r2, ssp-3.4.3.20050110-0, pie-8.7.7) 
OS:                Linux

In the subsequent kig file (lemniscata di Bernoulli), the name of Q1 does not follow its point.

cloc3@gentoo-amd ~ $ cat lemniscata.kig
<!DOCTYPE KigDocument>
<KigDocument axes="1" grid="1" CompatibilityVersion="0.7.0" Version="0.10" >
 <CoordinateSystem>Euclidean</CoordinateSystem>
 <Hierarchy>
  <Data type="int" id="1" >0</Data>
  <Data type="double" id="2" >0.00363649</Data>
  <Data type="double" id="3" >0.106254</Data>
  <Data type="double" id="4" >-0.280301</Data>
  <Data type="double" id="5" >-4.21244</Data>
  <Data type="double" id="6" >0.912603</Data>
  <Data type="double" id="7" >-0.0190581</Data>
  <Data type="string" id="8" >%1</Data>
  <Data type="double" id="9" >-0.0579768</Data>
  <Data type="string" id="10" >Q1</Data>
  <Data type="int" id="11" >1</Data>
  <Data type="double" id="12" >-7.84086</Data>
  <Data type="int" id="13" >0</Data>
  <Data type="double" id="14" >0.0248522</Data>
  <Data type="string" id="15" >%1</Data>
  <Data type="string" id="16" >%1</Data>
  <Data type="string" id="17" >M</Data>
  <Data type="string" id="18" >P</Data>
  <Data type="string" id="19" >%1</Data>
  <Data type="double" id="20" >6.94618</Data>
  <Data type="double" id="21" >-0.0455219</Data>
  <Data type="double" id="22" >0</Data>
  <Data type="string" id="23" >Q2</Data>
  <Data type="int" id="24" >0</Data>
  <Data type="int" id="25" >0</Data>
  <Data type="int" id="26" >-1</Data>
  <Data type="double" id="27" >-1.62232</Data>
  <Data type="int" id="28" >0</Data>
  <Data type="double" id="29" >0.0235768</Data>
  <Data type="double" id="30" >-0.0223149</Data>
  <Data type="string" id="31" >%1</Data>
  <Data type="double" id="32" >0.604285</Data>
  <Data type="string" id="33" >Circle 1</Data>
  <Object type="FixedPoint" id="34" >
   <Parent id="12" />
   <Parent id="6" />
  </Object>
  <Object type="FixedPoint" id="35" >
   <Parent id="20" />
   <Parent id="4" />
  </Object>
  <Object type="FixedPoint" id="36" >
   <Parent id="5" />
   <Parent id="27" />
  </Object>
  <Object type="RelativePoint" id="37" >
   <Parent id="22" />
   <Parent id="14" />
   <Parent id="35" />
  </Object>
  <Object type="CircleBCP" id="38" >
   <Parent id="36" />
   <Parent id="34" />
  </Object>
  <Object type="Label" id="39" >
   <Parent id="13" />
   <Parent id="37" />
   <Parent id="8" />
   <Parent id="18" />
  </Object>
  <Object type="ConstrainedPoint" id="40" >
   <Parent id="3" />
   <Parent id="38" />
  </Object>
  <Object type="ConstrainedPoint" id="41" >
   <Parent id="32" />
   <Parent id="38" />
  </Object>
  <Object type="LineAB" id="42" >
   <Parent id="40" />
   <Parent id="35" />
  </Object>
  <Object type="SegmentAB" id="43" >
   <Parent id="40" />
   <Parent id="35" />
  </Object>
  <Object type="RelativePoint" id="44" >
   <Parent id="7" />
   <Parent id="2" />
   <Parent id="40" />
  </Object>
  <Object type="Label" id="45" >
   <Parent id="1" />
   <Parent id="41" />
   <Parent id="31" />
   <Parent id="33" />
  </Object>
  <Object type="ConicLineIntersection" id="46" >
   <Parent id="38" />
   <Parent id="42" />
   <Parent id="26" />
  </Object>
  <Object type="ConicLineIntersection" id="47" >
   <Parent id="38" />
   <Parent id="42" />
   <Parent id="11" />
  </Object>
  <Property which="mid-point" id="48" >
   <Parent id="43" />
  </Property>
  <Object type="Label" id="49" >
   <Parent id="28" />
   <Parent id="44" />
   <Parent id="19" />
   <Parent id="10" />
  </Object>
  <Object type="RelativePoint" id="50" >
   <Parent id="9" />
   <Parent id="30" />
   <Parent id="47" />
  </Object>
  <Object type="SegmentAB" id="51" >
   <Parent id="48" />
   <Parent id="47" />
  </Object>
  <Object type="CircleBCP" id="52" >
   <Parent id="48" />
   <Parent id="47" />
  </Object>
  <Object type="RelativePoint" id="53" >
   <Parent id="21" />
   <Parent id="29" />
   <Parent id="48" />
  </Object>
  <Object type="Label" id="54" >
   <Parent id="25" />
   <Parent id="50" />
   <Parent id="15" />
   <Parent id="23" />
  </Object>
  <Object type="Label" id="55" >
   <Parent id="24" />
   <Parent id="53" />
   <Parent id="16" />
   <Parent id="17" />
  </Object>
 </Hierarchy>
 <View>
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="51" />
  <Draw width="-1" point-style="Round" namecalcer="10" style="SolidLine" shown="true" color="#0000ff" object="40" />
  <Draw width="-1" point-style="Round" namecalcer="33" style="SolidLine" shown="true" color="#0000ff" object="38" />
  <Draw width="-1" point-style="Round" namecalcer="17" style="SolidLine" shown="true" color="#0000ff" object="48" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="42" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="46" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="36" />
  <Draw width="-1" point-style="Round" namecalcer="23" style="SolidLine" shown="true" color="#0000ff" object="47" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="39" />
  <Draw width="-1" point-style="Round" namecalcer="18" style="SolidLine" shown="true" color="#0000ff" object="35" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="34" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="52" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="55" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="54" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="49" />
  <Draw width="-1" point-style="Round" namecalcer="none" style="SolidLine" shown="true" color="#0000ff" object="45" />
 </View>
</KigDocument>
Comment 1 Maurizio Paolini 2005-12-08 02:05:05 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.
Comment 2 Marco Clocchiatti 2005-12-08 09:58:10 UTC 
> 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.
Comment 3 Maurizio Paolini 2006-01-16 17:16:27 UTC 
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.
Comment 4 Andrew Crouthamel 2018-11-02 04:23:42 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 Marco Clocchiatti 2018-11-02 13:41:38 UTC 
(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.
Comment 6 Justin Zobel 2022-12-02 01:22:40 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 Marco Clocchiatti 2022-12-04 13:36:50 UTC 
(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.
Comment 8 Bug Janitor Service 2022-12-19 05:14:45 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 9 Bug Janitor Service 2023-01-03 05:28:10 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!