MoveToFitBounds / Screenbounds calculation Xamarin iOS

[boehlefeld]

Does Carto not resize and pan correctly on iOS binding when calling moveToFitBounds with reduced screen bounds?

Assuming following calculation on iOS side:

nfloat intHeight = UIScreen.MainScreen.NativeBounds.Height;
nfloat intWidth = UIScreen.MainScreen.NativeBounds.Width;
nfloat scale = UIScreen.MainScreen.NativeScale;
ScreenPos minScreenPos = new ScreenPos(50, 50);
ScreenPos maxScreenPos = new ScreenPos((float)(intWidth - 50), (float)(intHeight - 50));

MoveToFitBounds(mapBounds, ScreenBounds(minScreenPos, maxScreenPos), false, 1.5f);

Left side has more space than ride side. In case of ScreenPos(0,0) and ScreenPos(width, height) everything is fine.

Android works as expected.

Any idea?

[Edit] I may need to say, that in mapBounds exist a couple of coordinates. I just wanted to set a (scaled) delta to each side.

[Nikituh]

Hey

It looks like you're not using scale. iOS automatically translates to scaled coordinates, you need to multiply by the scale for it to be correct. Android's api returns actual resolution.

Either that, or your calculation is wrong. If you want "reduced bounds" to be centered, you need to substract double your padding/margin (your 50).

A sample of using Scale and MoveToFitBounds is available here: https://github.com/CartoDB/mobile-sample-data-collection/blob/master/iOS/MainController.cs#L220

[boehlefeld]

Thanks for the help. Solution was adapting only maxX, maxY. It gets centered afterwards.

nfloat height = UIScreen.MainScreen.Bounds.Height;
nfloat width = UIScreen.MainScreen.Bounds.Width;

ScreenPos minScreenPos = new ScreenPos(0, 0);
ScreenPos maxScreenPos = new ScreenPos((float)(width * 1.7), (float)(height * 1.7));