Prevent double clicks for point annotations

[dlangenk]

fixes #491

[mzur]

I can produce incorrect features with this change (the blue ones):

Screencast.from.26.07.2024.09.58.05.webm

If I try to delete one of those, the app crashes. The features that are created within the cool down period should be immediately removed again. Also maybe we could check if the new point is "near" the previous point (there should be an OpenLayers method for that)? If not, users should be able to create points faster than the cool down period (as in the video).

[dlangenk]

If i throttle my connection speed I also see that problem. Before I simply could not reproduce that.

[mzur]

Strange, it should not have anything to do with the connection speed. This is purely client-side. You have to click faster than the 400 ms for this to happen.

[dlangenk]

I guess now the point is removed after all, BUT the map is also dragged after a double click. I also added the distance to last annotation feature.

[mzur]

I've updated the code a bit so the point and time are only updated if drawing points. However, this still fails because there is no distanceTo() method in an OpenLayers geometry. LLM fail? 😄

This is likely also the reason why the map is "dragged" for you because there should be a JS error in your console.

[dlangenk]

Pretty sure that I actually got a distance and no error, but I'll have a look at this. No LLM fail😉, but rather StackOverflow

[dlangenk]

Don't know why the console error slipped. Now it works, without any errors ;-) Please have a look if the position of the computeDistance function is correct or if it should be somewhere else.

[mzur]

The distance calculation works but the feature wasn't removed for me now, too. This was because the feature is added to the source after the drawend event was handled. I fixed that now.