Hemisphere Mercator Glitch

[Piotr]

When I set Mercator to a hemisphere, it crashes the computer.

[Atarimaster]

When I set Mercator to a hemisphere, it crashes the computer.

What do you mean with »set Mercator to a hemisphere«?
Something that’s got to do with hemispheric interruptions, or some settings in the Boundaries dialog?

[Piotr]

When I set Mercator to unconstrained, or corners from 90, -180 to -90, 180 it works fine. But it crashes when I set it to a hemisphere, at least the Eastern one centered at 70.

[daan]

When I set Mercator to unconstrained, or corners from 90, -180 to -90, 180 it works fine. But it crashes when I set it to a hemisphere, at least the Eastern one centered at 70.

Clearly a bug, but I think the responsible thing to do here is not to include the poles in your bounding box, since that’s not meaningful anyway.


— daan

[Piotr]

When I set Mercator to unconstrained, or corners from 90, -180 to -90, 180 it works fine. But it crashes when I set it to a hemisphere, at least the Eastern one centered at 70.

Clearly a bug, but I think the responsible thing to do here is not to include the poles in your bounding box, since that’s not meaningful anyway.


— daan

Did you fix it in the upcoming version (3.2)?

[daan]

Did you fix it in the upcoming version (3.2)?

No. And, as you know, 3.2 is not “upcoming”.

— daan

[Piotr]

Did you fix it in the upcoming version (3.2)?

No. And, as you know, 3.2 is not “upcoming”.

— daan

Then what version is "“upcoming”"?

[Atarimaster]

"upcoming" means "soon to be released".

A while ago, the current version was 3.1, but the work on 3.2 was almost finished, so 3.2 was "upcoming".
Now, 3.2 is the current version. For the moment, there might be no upcoming version at all (in case daan doesn't plan to release an update soon), but if there is, only daan knows which version number it’ll have.