Answering my own post. I think I've discovered the source of the reload problem. One of the NWS radar image .geo files I had activated had a 60 second refresh rate. Every time the radar image refreshed, it triggered a refresh of the OSM layer. That resulted in a download/cache test every minute.
If I remember correctly, the current code can't render each layer independently of the others so when one layer refreshes, all of them must be redrawn in the layer order. If I'm correct then the entire window gets redrawn every time one of the layers updates including the radar images. I didn't notice the radar image at first because it was actually way off screen. I started searching the .geo files for a refresh rate and found it in the file used by the radar image. --- On Sun, 4/3/11, Alex Carver wrote: > I just noticed my copy of Xastir is > attempting to download the OSM tiles about once per minute > or faster. I looked around the .geo file and in the > timings dialog but there's nothing controlling the download > rate of the tiles. > > The reason I ask is because Xastir consumes 100% CPU and > pretty much blocks everything until the download/cache check > is done. > > Is the rate hardcoded or is there a soft config setting > somewhere that I overlooked? _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
