<div dir="ltr">Hi. I had a similar problem and it apparently had to do with the CRS which in my case was not a projected one. Check this out only to discard possible solutions.<div>Regards,</div><div>Sergio (Uruguay)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/1 Gilles Delaunay <span dir="ltr"><<a href="mailto:delaunay@belziger-industriepartner.de" target="_blank">delaunay@belziger-industriepartner.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear users/developers of Gvsig,<br>
<br>
I could not find a "submit bug" tracker in the Gvsig community, so I<br>
assume this list is the right place to discuss a strange "feature" of<br>
Gvsig which could be a bug.<br>
<br>
My problem: the "measure distance tool" of gvsig behaves strangely, it<br>
is unusable. It goes up and down as I increase the distance I want to<br>
measure with the mouse.<br>
For example: I click an "origin" point on the map, move a bit: the<br>
distance shown at the bottom right of the GUI increases quickly. I move<br>
further: it goes down. I move further: it goes up again, like a<br>
periodical function. The function also seems to be periodical when I<br>
change the angle of the distance measured (move the mouse without<br>
changing the distance to the origin). I could not find any rationality<br>
in the function: just ups and downs.<br>
The function "measure area" from the GUI has the same problem (I guess<br>
the "area" function uses the "distance" function). The functions "Area"<br>
and "Perimeter" of the "Expression calculator" in the Table view have<br>
the same problem. I assume they use the same (bad) functions.<br>
NavTable shows the RIGHT values. The Buffer function of the SEXTANTE<br>
plugin works correctly: I assume those plugins use their own (good)<br>
distance and area functions.<br>
<br>
I use Windows 7 Pro 32bit.<br>
I have several versions of gvsig installed on my system, from 1.10 to<br>
2.0., including CE and OADE. They all have the same problem (with many<br>
many more problems and bugs for 2.0, but this is another story). I have<br>
several versions of Java installed on my system: 1.7.0_25 and 1.6.0_26.<br>
I tested both (disabled one of them in the Java control panel): it did<br>
not solve the problem. I tested several coordinate systems: it did not<br>
solve the problem.<br>
I could not find any trace of a similar bug on the internet: am I the<br>
only one in the world with that problem?<br>
<br>
Your suggestions?<br>
Do not hesitate to answer in spanish: I can read it, but my spanish is<br>
not so good that I can describe a bug "en castellano".<br>
<br>
Thanks<br>
<br>
Gilles Delaunay<br>
from Berlin<br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
<br>
To see the archives, edit your preferences or unsubscribe from this mailing list, please access this url:<br>
<br>
<a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
</blockquote></div><br></div>