"Ed Loach" <[EMAIL PROTECTED]> writes: > I may have mentioned it before, but if someone is using (an > unmodified) tah.pl as the Windows frontend, then when you click > Start it rebuild tilesAtHome.conf from tilesAtHome.conf and some of > it's own settings that it stores in the Windows registry. If you > want to change any settings that can't be set within tah.pl then you > have to modify one of the local copies of the files that are > controlled by svn. > > As I now see, Olf made his changes in TilesAtHome.conf.windows, > which will break the svn update. There is no way with that Windows > frontend to set RenderStripes in any other way though. I gave up > using it and have written my own (in VB 2008). I'd offer to share it > but presently all the paths are hardcoded (in one function which has > a ToDo to get them from a settings file somewhere). > > One workaround, Olf, is to modify the tah.pl file and delete the > section of code shown below from somewhere around line 450 in sub > start_tah. You would then change settings in TilesAtHome.conf and > not touch the .windows file at all. I suspect any changes you make > via the tah.pl interface may not work, though from a quick look the > bit that updates authentication.conf should still work, as *might* > the bit about proxies.
Is it worth going through that much pain just for not having to run the client from the command line? I have no clue myself since I have never tried to do that on Windows. If it is that much desired to have a Windows frontend (and maybe an X frontend) I would suggest to develop that in OSM SVN to make it easier for client developers or anyone else to make modifications that are necessary because of client changes. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
