#402 Mobac fails to start if "last source loaded" has an error

[Laurent Grenet]

I found this bug in my 2.4Beta13 testing, but after verification, the same bug exists already in 2.3.3, so I preferred to create a bug ticket rather than a comment in the discussion thread relative to 2.4Beta

Assume that the last time you run MOBAC, you were using the source XYZ, that was OK at this time.
Then when you restart MOBAC, for any reason, the source file XYZ contains an error.
This can happen

• either because the condition of MOBAC have been modified in the meantime,
• or because a modification has been done in the XYZ.bsh file

In my case, this source XYZ had a maxZoom = 22, that was acceptable up to beta12.
But when I restarted MOBAC beta13, using the same settings.xml than with beta12, this value for maxZoom is no more acceptable, and the bug occurs.

The result is that MOBAC display a perfect error message (and that's OK).... but never ends loading the DefaultMapsource or the WorldMap, as it would have done if XYZ source was no more available.
The MOBAC logo remains on the screen, and the ONLY way to stop it, is to cancel the Javaw.exe task in the task manager.

[r_x]

Nice finding. An uncloseable splash screen ;) I fixed that in the source code.

I also added validation logic for checking the minimum and maximum zoom level of loaded custom XML and BSH map sources.

So this problem is fixed on multiple levels. It will be included in the next beta version.