[VTM][Android] VectorLayer update problem

[Jaca]

Hi Emux, ;-)

I have a problem with the VectorLayer. Could You check why a shape on the VectorLayer doesn't display very often after starting VectorLayerActivity?

Use VectorLayerActivity from vtm-android-example and:

1. change number of shapes to one

2. increase size of shape

3. change position to fixed GeoPoint(0.0f, 0.0f)

4. run example several times...

The map needs to be moved to refresh (and display shape) very often.

ps. I'm testing modified VectorLayerActivity from vtm-master which has vectorLayer.update().

[Emux]

> I'm testing modified VectorLayerActivity from vtm-master which has vectorLayer.update().

The sample with the vectorLayer.update() shows one or multiple shapes every time it runs.

--
Emux

[Jaca]

...but vectorLayer.update() doesn't work 10/10 (100%) startups. I've the same issue on my app when it starts up.

[Emux]

I can only try the sample and it shows the shapes every time it starts in my tests.

(but needs the update call in the right place)

--
Emux

[Jaca]

Take a look.

[Emux]

Like already mentioned, I cannot reproduce it.

You can also try the following calls after adding all layers:

map.render();

or

map.clearMap();

--
Emux

[Jaca]

Workaround:

Style.Builder sb = Style.builder()
.buffer(0.5)
.fillColor(Color.RED)
.fillAlpha(0.2f);

for (int i = 0; i < 1; i++) {
Style style = sb.buffer(10.0)
.fillColor(Color.RED)
.fillAlpha(0.5f)
.build();

vectorLayer.add(new PointDrawable(0, 0, style));

}
//vectorLayer.update();
mMap.postDelayed(new Runnable() { <<----

@Override
public void run() {
vectorLayer.update();
}
}, 100);

mMap.layers().add(vectorLayer);

[Emux]

It is important to call the vectorLayer.update() at the end (like in the sample)
and then everything should work like with the example.

--
Emux

[Jaca]

As You see, I've vectorLayer.update() in Runnable and it started working 100/100. :-)

[Jaca]

...and my app too.

[Emux]

It may depend on your implementation or Android or device or ...

There are many factors and applications should use library API accordingly.

Anyway it is nice that you found a solution for your case.

--
Emux

[Jaca]

Tested on Galaxy S9+ and Galaxy Note 10. Please note that the issue only occurs when the map is starting. After this the map refreshes properly by vectorLayer.update() (without Runnable).

Thank You for Your work.

[Jaca]

Next (better) solution:

mMap.events.bind(new org.oscim.map.Map.UpdateListener() {

    @Override
    public void onMapEvent(Event e, MapPosition mapPosition) {
       if (e == Map.CLEAR_EVENT) {
          vectorLayer.update();
       }
    }
});

ps. Probably the problem is related to map initialization time (map is busy while executing vectorLayer.update()).