[Xastir] Dbfawk reload

[Tom Russo]

On Sun, Dec 26, 2004 at 12:57:44AM -0700, we recorded a bogon-computron collision of the <jewen at shaw.ca> flavor, containing:
> > So if you're doing tons of development on a dbfawk file, 
> > don't put it in /usr/local/share/xastir/config, just give it 
> > the same base name as the shape file you're working on and a 
> > ".dbfawk" extension, and put it in the same directory as the 
> > shapefile.  You can then edit it and have its effects visible 
> > just by going into the map chooser and clicking "ok" to 
> > redraw the display.  Only when you're done editing your 
> > dbfawk file and want to set it in stone should you move it to 
> > the config directory and let it be used as a per-signature file.
> > 
> > Not the best solution, but certainly a viable work-around.
> 
> I guess I'll just have to restart Xastir every time I make a change. I have
> cut up the shapefiles into over 40 chunks, so to be able to have the effects
> show on all of them, I'd have to edit 40+ dbfawk files.

Or wait 5 hours for anon cvs to catch up with development cvs.  

I just slammed in an utterly trivial hack that causes stored dbfawk signatures
to be flushed when "add new maps" or "reindex all maps" is chosen.  When you 
do your cvs update, if map_shp.c contains "clear_dbfawk_sigs" then you have 
the fix.

Once you have it you can do your dbfawk hackage, click "add new maps" and then 
force a redraw (Map Chooser->"Ok" would be enough) and all the dbfawk file 
should be re-read.

HTH,
T.

-- 
Tom Russo    KM5VY     SAR502  DM64ux         http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://www.qsl.net/~km5vy/
 "When life gives you lemons, find someone with a paper cut."