[Xastir-Dev] Re: [Xastir] geo files again
Reuven Z Gevaryahu
gevaryah at netaxs.com
Fri May 2 14:42:51 EDT 2003
Curt Mills, WE7U wrote:
> On Fri, 2 May 2003, vic wrote:
>
>>Where in the documentation of xastir does it say that the geo files HAVE to
>>look like this???
>
>
> The docs may not have caught up to the code in this instance. I
> don't think IMAGESIZE was initially required, but it might well be
> now. It was probably the work I did on keeping track of the map
> extents where IMAGESIZE became a requirement. Without it, it's
> difficult to know when to load the maps, unless we make some queries
> through ImageMagick calls to compute the image size, which we don't
> currently do (something to implement for the future).
>>1. not seeing a geo file without the display option.
>
> I'm assuming you mean the IMAGESIZE option. Looking at the code,
> these appear to be required options now, as you stated. I just
> changed the help-English file to match.
>
This was something of an unfinished discussion from last year. I had
left the docs untouched in the hope that it would get fixed. Basically,
when the extent caching was added, it made the extent calculation (done
using imagesize) manditory. The old code would load the image regardless
of if it was on screen if there was no imagesize, and would load
onscreen maps if we knew the imagesize. I think the old behavior is
desirable, or the imagesize should be calculated by opening the image
when indexing. (like the identify command)
As things stand now, we just totally killed compatability with WinAPRS
.geos with this requirement. I nominate this for a "blocking release" bug.
--Reuven (KB3EHW)
More information about the Xastir-dev
mailing list