From 32423ca04339f0f3e4c71bb4de2a762d1a8b2bad Mon Sep 17 00:00:00 2001
From: cignoni <paolo.cignoni@isti.cnr.it>
Date: Thu, 31 Jan 2013 10:44:44 +0000
Subject: [PATCH] Improved comment on the order of the returned elements in a
 kdtree

---
 vcg/space/index/kdtree/kdtree.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vcg/space/index/kdtree/kdtree.h b/vcg/space/index/kdtree/kdtree.h
index f3af114c..1aef91cd 100755
--- a/vcg/space/index/kdtree/kdtree.h
+++ b/vcg/space/index/kdtree/kdtree.h
@@ -165,7 +165,7 @@ void KdTree<Scalar>::setMaxNofNeighbors(unsigned int k)
         * a simple stack is by far much faster.
   *
   * The result of the query, the k-nearest neighbors, are internally stored into a stack, where the
-  * topmost element
+  * topmost element [0] is NOT the nearest but the farthest!! (they are not sorted but arranged into a heap)
         */
 template<typename Scalar>
 void KdTree<Scalar>::doQueryK(const VectorType& queryPoint)