[Xastir-Dev] Re: [Xastir] geo files again

[Curt Mills, WE7U]

On Fri, 2 May 2003, Reuven Z Gevaryahu wrote:

> 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.

I could see doing that.  It'd give me time to verify the RELAY
digipeat code was working properly as well.  I'm also now working on
some of the bugs that Dale Huguley just came up with.

Does anyone know if the ImageMagick API has an easy way to determine
image size in pixels?  If so, I could add that in as part of the
indexing and this problem would go away.

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_ at tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"