had a flash look to gmaps custom overlays (assuming this is what you are talking about) and you should have everything you need (onAdd, draw, onRemove)
1 Like
Yes, the draw will probably do, I’ve used it already and it does exactly that 
@Broberto, you provide an unfair and inaccurate assessment of WeWeb support priorities and processes.
We receive hundreds of support requests and questions from users weekly through the different channels - Slack (Enterprise), Online Chat (Business Workspace), and then here, through the community.
We have a very robust prioritization process that determines how we address the various requests. This process takes into consideration various parameters such as the severity of the issue, the frequency with which it might occur, the number of users it might impact, the financial considerations of such impact, the user/customer reporting the issue, etc. etc.
The process determines in what order we address the issues (or if we address them at all) and then we go to work.
This community differs from other channels in that it is public, and other users have the option to respond to issues before we do, and thanks to the great community we have, they do.
If an issue reported here in the community goes unanswered for a while we might address it ourselves but that is secondary to the community answering. So the fact that @dorilama or other answer issues before the WeWeb team is exactly how it should work and it indeed works very well.
The priority of our team is to answer issues reported through the 1:1 channels because the general public (community) can’t answer those - only we can. Also, those customers “pay for the privilege” of getting quick answers.
You have access to online chat and are welcome to ask any questions through that online chat - you will get serviced like every other WeWeb Partner. In fact, all WeWeb Partners use the online chat for support issues, not the community. When it comes to bugs, Daniel, I and everyone else from WeWeb keeps repeating the same thing over and over again - write a ticket so it can be logged, tracked and processed properly.
This community is not for that.
Lastly, why has no one from the WeWeb team responded to many of your issues posted on the community? Because they are mostly “edge” issues - they are important to you, but in a grander scheme, they don’t pass through the various other criteria for prioritization.
We really value your contribution to the community, you are doing an amazing job here. But accusing the hard working WeWeb team on ignoring your requests and being dismissive of their work devalues that substantially.
- If you find a bug, write a ticket
- If you have a question or an issue that requires quick response, use the online chat.
Thanks you for understanding and keep up the good work here.
3 Likes
Hello Slavo, thanks for the clarification. While I don’t agree with some parts, I agree that I’ve been harsh. I’ve been harsh, out of despair, because there is not enough interaction with people like me who pour their life literally into WeWeb.
That just brings me to the thing that more people, not just me think. The amount of support and engagement is not enough, it might be great job but it is not enough.
If you take out the emotion from my comments, I think you’ll find a clear message, that I hear too often from everyone who comes to consult, or even among the clients and creators in the WeWeb space.
“We need better support and more interest within the community from the team.” Now it is not enough. This is the general consensus, that you might not hear, but I heard it loud and clear. And I’ve been voicing it loud and clear, as I am now. One thing is sharing the nice things people do on Socials, the other is actually going into the trenches. Currently it simply is not enough.