Build number: 2010.01.18.1 system : pmpc973

to reproduce, the files are located in users/rsg/arsf/workspace/GB07_07-2009_277_inverclyde/leica/proc_laser. start up lag with no arguments, file, open, select the file LDR091004_131017_1.LAS and click add. Then select the file LDR091004_122647.LAS and click add, instead of simple adding the new line to the display (already showing the first line) an error message is printed to the command line. this is also true if you try to load both at the same time. However it does not occur if you open every file or other certain combinations.

If you open /users/rsg/arsf/arsf_data/2009/flight_data/uk/UR09_01-2009_327_Flood_Cumbria/delivery/20100107/UR09_01/ascii_laser/LDR-UR09_01-200932701.txt in LAG, it doesn't produce an error but comes up blank. If you alter the point size it then comes back, but is apparently not the same problem as what happens if there's a point a long wway out of bounds.

a feature is desired which allows the user through a pop up box when loading files to be notified that the selection will overflow the available ram and use swap space, they will then be given 3 options, abort, continue, or use hard drive/main memory caching.

abort does what it says on the tin as does continue (which should have a warning message pointing out that your about to have your swap filled and this will make the machine unresponsive and cause serious problems if the machine runs out of swap memory)

the third option will cause the flight lines to be loaded but to be stored on the hard drive rather than in ram. This will provide stable access to full resolution data at the cost of speed.

wish list: the program will be intelligent about the cashing, loading in the most relevant data to main memory to reduce response time when the user is only viewing a small portion of the data

the program will be multi threaded allowing data to be pulled off the hard drive while the user is still using the gui. for instance while the users is zooming in and out of a small area, a larger area around it is being moved to main memory in anticipation of the user viewing it.

supplemental to this any and all options to further reduce the memory footprint of loaded flight lines need to be looked at