Arnold Harding - KQ6DI
Are all / any of these map changes going to break what I already have? I have Thunder Landscape working fine, but it sounds like all of my map stuff is going to get scrambled. Since I don't know what Meta/MB tiles are, it's a bit of a worry.
So if you could just give a simple explanation of what the Meta/MB file structure changes are going to destroy in my current tile file structure system, it would be nice.
By the way, the 2020/05/14 10:48 version takes a lot longer to exit/close the program than anything previous. I just timed closing the program at 11 seconds after I hit "Really close? YES". And that's after only having the program running for 15 seconds.
Interspersed comment below...
On 5/15/2020 12:57 PM, Arnold Harding. - KQ6DI wrote:
The plan is to continue to support file-system-based tile storage
for the foreseeable future. It's just really space-wise
inefficient and hard to copy/move/share with others. So you can
rest easy knowing that I try not to be that short-sighted!
That's a good idea. I'll have to cobble up a Wiki explanation page once I figure out what the final look will be. I'm hoping that all NEW Tile Sets will be created with MBTiles databases rather than file-system-based storage. Only existing (and non-migrated, see e-mail about Migrate) Tile Sets will continue to use the individual tile files.
That is worrisome. Do you have any *.dmz or *.dmp files showing up in the runtime directory? It almost sounds like it's dumping itself during the exit.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and