Robert G Birch

I am happy to insert the suggestions made above if this helps you to update the README file. Is it OK to use notepad++? Should the suggested additions be marked somehow? I can add the available atlas formats to the README list, but I do not know the technical details comparable to those provided for existing formats in the list. It is quite useful for users to know such things, for example the special features of any format. Are you (or someone else) willing to add the technical details?

Hi r_x. Thanks again for the suggestions. To answer your question: my system has 16GB physical ram and a paging file managed by Windows 10. This may be the limitation, but it is strange that it applies at the point of area selection and only when the selection is close to the MOBAC display area (and with so few tiles). Anyhow, it is easy to work around (once one knows the trick) by keeping the selection area well within the display area - then it works fine with my system even if thousands of tiles...

Thanks r_x. I am a map user (not a computer scientist or program developer), so I will not understand everything. But it may still help you or other users when I report: I do not know why MOBAC/Java complains when the selection is close to the display size . We users can avoid the problem once we know about it. In case it helps you I have tried to attach a doc file including some of the Java clipboard reports (many other times hung without such a report) and a screen-grab that illustrates what was...

A couple of observations that may help: MOBAC hangs after lots of CPU use and a Java outofmemory exception if the area selected is very close to the area displayed. It does this on “Add selection” from multiple WTMS soures, to multiple atlas types, and in two tested MOBAC versions. I was working with only about 15 WTMS tiles at zoom 15. Everything is fine if the area selected is well inside the area displayed. MOBAC readme says under the Garmin Custom Map heading that if a map is larger than 1024x1024...