r_x

You can change the maximum RAM/heap size of Java by creating a file Mobile Atlas Creator.ini next to Mobile Atlas Creator.exe. In the ini file just put one line of text -Xmx8g and save it. Next time you start MOBAC using exe file MOBAC will have access to up to 8GB of RAM. Regarding the update to Readme.md file: You can find the latest version here: https://sourceforge.net/p/mobac/git/ci/main/tree/README.md Just download the file, add the information you think that is missing and then send me the...

Java provides two way to parse an URL from a String. The old way is new URL("http://example.org"). This way is now deprecated. The new Apache commons http5 client uses internally the new preferred way new URI("http://example.org") which handles some cases like | characters different.

HI Robert, just took your latest and joined my additions from July - well, Claude did ;-). It includes an .md file for what, why and how. Cheers Michael Edit: The discussion about the mentioned additions has been moved to a different thread: https://sourceforge.net/p/mobac/forum/general/thread/f0ae87fdd0

Hi Robert, coming back to your ask, here are my comments (assuming that you kept the zip file with the java patches as well as the .md): 1) original MOBAC 2.3.x and betas fail at the border areas between two or more layers with mapsforge maps: one of the pair "wins" and can leave part of bordering tile blank. The fix patch merges the "overlapping" tiles taking all relevant data from both. This also includes a "debug" feature by which you can specify x/y/z and a target directory to dump each layer...

MOBAC is an open source project. Feel free to participate and provide detailed documentation. We can e.g. create a page for Garmin devices in the Wiki: https://sourceforge.net/p/mobac/wiki/Home/ How much RAM does your system have? I have seen in the OutOfMemory error messages that MOBAC is by default limited to 4GB. MOBAC can be started with additional configuration to allow using more RAM - if you have.

Please check 2.4.0-beta6, display name collision should be automatically resolved. BTW: Even when a map source has the same name in the map source list/tree in the main UI, the tooltip should reveal the actual map source that is behind an entry. After releasing beta6 I identified the reason why the map source list behaves so oddly when there are multiple map sources of the same name. So even if there would be multiple entries showing the map source (display) name, the entries would be correctly ...

bugfix: when clicking a map source in the list of available map sources directly get the map source; do not try to get the map source by its (display) name

A new beta version of MOBAC has been released. You can find it in the section Alpha and experimental. Changes since 2.3.3: Dialog "Select distance around track" allows to increase the slider range BSH map sources: updated BSH library to 3.0.0 snapshot ensure compatibility with latest Java versions Mapsforge library updated to version 0.30.0 Map Evaluator: loading of Mapsforge custom maps fixed Added support for PNG 16 and 256 colors with transparency (PNG 4bit/8bit) Color reduction now performed...