[glitch] visual glitch in treemap on zoom

[insignis]

SpaceMonger 2.1.2-pre3 in normal mode
Windows XP SP2
Bug in: treemap
Severity: minor/glitch/annoyance
What I was doing: zooming in as far as I could. At a point, not much beyond a single file filling the screen, the entire treemap goes completely blank (the color of the topmost directory level). Can zoom back out and the treemap will pop back and work fine. I was scrolling with the mouse wheel if that matters.
Anything else: large (1.75 TB) volume, lots of files. I've taken the original scan file and cut out swaths of it to get it down to a manageable sized file that still produces this and the other bug I reported today. Now at 51 megs (3.5 rar'd). Will email to you with instructions to reproduce. I could not reproduce this bug anywhere on my local C drive and not everywhere on the saved scan. It seemed to favor densely populated directories.

[seanw]

At a point, not much beyond a single file filling the screen, the entire treemap goes completely blank (the color of the topmost directory level). Can zoom back out and the treemap will pop back and work fine. I was scrolling with the mouse wheel if that matters.

I've tried and tried and tried to reproduce this with the scanfile you gave me, but with no success. Every time I try it, it works perfectly; is there something more specific you can tell me about how to reproduce it?

[Gray]

I have also rarely encountered this issue. It generally when zooming in on the edge of a dense area. If you keep zooming it sometimes does stop displaying and changes to the solid color. This happens with a regular scan as well and not just a scanfile.

[insignis]

I've tried and tried and tried to reproduce this with the scanfile you gave me, but with no success. Every time I try it, it works perfectly; is there something more specific you can tell me about how to reproduce it?

For the forum'ers: We continued this conversation via email... I hope it's okay to reproduce here, Sean?

Yes, actually. I tried it again and realized there's another factor. It only happens in "full screen" mode (whatever the name is for that
extra title bar button). Zoomed in as far as I could go in the middle
of that folder, I was able to effectively turn the bug on and off with
that button.

I see it now; and I think you're running at a much higher resolution than I've been testing at as well, since I wasn't able to get it to reproduce itself at anything less than 1600x1200. It appears to be a numerical rollover issue as well; the numbers get a little too large for their own good, and suddenly become impossibly small (or zero). This should be fixable, but it'll take a little bit of time to figure out where to get some additional precision to correctly display the result.

Yes, fullscreen mode, maximized at 1600x1200 (and dual monitors, though it's not easy or pretty to stretch it over both, really).

Yeah, it's not quite that big a deal, but I would like to fix it. I think what's happening is that you're actually blowing out 64-bit int (you're generating numbers that are too large for it), so the results are getting rounded to zero instead of to a very large value. I've been trying to avoid converting the layout math to floating-point, because there's a performance hit there, but that may be the only solution left.