Custom Query (432 matches)
Results (91 - 93 of 432)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#307 | fixed | real time point slection while draging cursor | emca | chrfi |
Description |
to further expand the functionality relating to selecting a point and seeing information on that point. allow the user to hold down right click and move the mouse over points, when the cursor gets near a point the information appears. at low zoom levels this would allow the user to click and drag there mouse over the points (as their zoomed out it will almost always be selecting a point) and see the changing values. useful in seeing height changes, intensity changes, etc. needs to be real time and smooth but this shouldn't be too hard with the speed of the subsetting methods (hopefully :D ) |
|||
#308 | fixed | fedora 12 missing text under buttons | emca | chrfi |
Description |
system : pmpc974 Build number: 2010.01.26.1 if you run lag in fedora 12 you lose the text beneath all of the buttons in the main view. |
|||
#311 | fixed | drawing the flight lines increases main memory usage | emca | chrfi |
Description |
to reproduce load several flight lines that will not fit within the given cache. these will load normally with the ram usage being capped at the cache limit. when the image is first drawn the amount of ram being used by the program will increase. This increase seems to be linked to the size of the flight lines. subsequent redraws increase the ram usage slightly but i think this is the same problem being caused by drawing areas that were in cache the first time but now have to be loaded. once each part of the image has been drawn and loaded out of secondary memory once the increase stops. This at first seems to point to a problem in the caching code and therefore i have used my test bed to perform unit tests on the quadtree and caching classes. These tests showed that without the gui loading and then pulling points out of uncached buckets has no effect on the ram usage of the program. so far the only theory is that it is caused by an overflow from the graphics card ram. |