Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose rendering context in API #2003

Closed
htulipe opened this issue Apr 21, 2014 · 1 comment
Closed

Expose rendering context in API #2003

htulipe opened this issue Apr 21, 2014 · 1 comment

Comments

@htulipe
Copy link
Contributor

htulipe commented Apr 21, 2014

AFAIK, there is no method/member in the current API that can tell which rendering context is used by the map. This information could be useful.

For instance, some times ago, default renderer has been changed from WebGL to Canvas. This change caused a malfunction in bind inputs example where hue, saturation and brightness inputs are no longer relevant in Canvas context. This results in a buggy-like example. One could easily fix that by disabling those inputs unless WebGL rendering is used.

IMHO, this case illustrates the need to make rendering information available to developers.

I would see something like: map.renderingContext which would be a string (webgl, canvas or dom).

If this make sense, I will make a PR.

@htulipe htulipe closed this as completed Apr 21, 2014
@htulipe
Copy link
Contributor Author

htulipe commented Apr 21, 2014

Duplicate of #2004, my bad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant