Insert / Retrieve seems to be wrong about quadtree-js HOT 3 CLOSED

Hey, again sorry for the late response, didn't see the issues here.
This may be intended use and a misunderstanding. Some example code would be awesome.

What I understood you tried to achieve something like this? http://jsfiddle.net/ua9203zb/2/
It has a 4000x4000 area with 4x4 possible quadtrees, limited by the max_levels of 2.
The top left 1000x1000 is constantly retrieved and those objects are highlighted in white.
(Draw functions are scaled down by 10)

from quadtree-js.

Yes, your setup is right and this screenshot shows, what I find unexpected with it:
http://s27.postimg.org/63s8wzt4z/Quadtree.png

But if I remember right, it just occures with non-point Items. It is totally fine, when you just use point-dimensional items

I modified your example a bit: http://jsfiddle.net/zwcckn5s/
All retrieved tiles are drawn in blue when you query for the upper left corner (0, 0, 1000, 1000)

from quadtree-js.

I did some updates on the code and came across this post one again.
Like I said in the other issue months ago, the screenshot shows intended behaviour since the Quadtree only narrows down the objects of possible collision.

The problem in your example is the dimensions of the objects, they are 1000x1000 units, aligned in a grid. Same grid as the Quadtree, I don't see the actual point in this? They cannot fit into one exact subnode, since they are same size. This is where the screenshot effect comes in: all objects touching a shared border with the retrieve area are possible candidates.

When you debug myTree in the given example, you see that all objects belong to the master node, the Quadtree itself.

I reduced the objects dimensions by 2 units, this way it works http://jsfiddle.net/zwcckn5s/1/
When you debug there, objects are stored in subnodes, the way it should be.

There are new examples and docs, maybe check them out.

from quadtree-js.