OK, I found what I think are the relevant functions, index_*() in map.c, and the structure definition in map.h.
Here is what I think is being asked: At present map_geo.c does not open and read the .geo file during indexing, but that would be changed (slowing the indexing, but perhaps acceptable). Then the index_update_xastir() API would be changed to allow additional information to be passed in (like zoom mode, projection type, name of a copyright file, etc.). Once the index has the information then the Map Chooser would be turned into a larger dialog (or one with a horizontal scroll bar) so that the additional information can be displayed. But that probably does not provide enough room for extended text such as copyright strings and an explanation of the zoom operation. So I'm not sure that will work... Is this the right track? Is it worth it? 73, ...jerry On Thu, Jun 17, 2010 at 4:01 PM, Curt, WE7U <curt.w...@gmail.com> wrote: > On Thu, 17 Jun 2010, Jerry Dunmire wrote: > >> I probably misunderstood in that I thought that map_index.sys was >> just a cache. I'll look at how it gets generated. > >> From Map->Configure->Index > > >> Just looking at the present format for map_index.sys, it doesn't it >> look like it would be a good choice for arbitrary notices (such as >> copyrights, etc.), but adding flags is probably not difficult. > > Perhaps a pointer to a filename to spit out when flags specify to do > so? > > -- > Curt, WE7U. <http://www.eskimo.com/~archer> > APRS: Where it's at! <http://www.xastir.org> > Lotto: A tax on people who are bad at math. - unknown > Windows: Microsoft's tax on computer illiterates. - WE7U. > The world DOES revolve around me: I picked the coordinate system!" > _______________________________________________ > Xastir-dev mailing list > Xastir-dev@lists.xastir.org > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev > _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev