You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2021. It is now read-only.
So on my side I have worked out marker annotations that are persistent, clickable, one at a time (you are allowed to select multiple with ctrl+click which I think is a good idea if you wish to track 2+ trains) and follows the marker. Currently it does somewhat overlay the marker in some positions as it pops up either up or down based on how much room is available like so.
I think just lowering the opacity of the speech bubble part world work. The way I have this does involve a change of making the current markers into vectors and also changes the code towards reusing the markers it creates which I believe would be a step in the right direction with reducing the load on clients.
I have gotten it working with the current code base (but it currently lacks, updating, 1 at a time and doesn't really tell which market it is about)
Any suggestions?
The text was updated successfully, but these errors were encountered:
One immediate suggestion is to have the base of the bubble be on the right middle of the marker icon. Opacity will help with viewability. I would suggest taking away mouseover popup and making it persistent with a click if that's now the current behavior already.
Create a branch to play around with it and I'll take a look as well.
So on my side I have worked out marker annotations that are persistent, clickable, one at a time (you are allowed to select multiple with ctrl+click which I think is a good idea if you wish to track 2+ trains) and follows the marker. Currently it does somewhat overlay the marker in some positions as it pops up either up or down based on how much room is available like so.
I think just lowering the opacity of the speech bubble part world work. The way I have this does involve a change of making the current markers into vectors and also changes the code towards reusing the markers it creates which I believe would be a step in the right direction with reducing the load on clients.
I have gotten it working with the current code base (but it currently lacks, updating, 1 at a time and doesn't really tell which market it is about)
Any suggestions?
The text was updated successfully, but these errors were encountered: