Emil Haldrup Eriksen

It does not seem that way. However, there is a Python3 branch (which seems to work).

You could try the `Keyboard` component in dash-extensions, ``` import dash import dash_html_components as html import json from dash.dependencies import Output, Input from dash_extensions import Keyboard app = dash.Dash() app.layout...

@alexcjohnson Thanks! As the components mature, i think it would be good (in particular for new users), if they were moved to `dash-core-components`. The `Trigger` component would probably be a...

The `Keyboard` component was removed in favor of the more general `EventListener` component. While the latter does have feature parity (and beyond), the syntax is a bit more convoluted, so...

One possible workaround could be to use the `CycleBreaker` transform from `dash-extensions`, https://www.dash-extensions.com/pages/transforms/cycle-breaker-transform

I am also interested in progress on this PR. As I understand, it would enable people to wrap leaflet plugins as separate Dash components, and use them with `dash-leaflet`. Which...

As a workaround, you could try the cyclebreaker transform, https://www.dash-extensions.com/pages/transforms/cycle-breaker-transform

I am experiencing the same issue. How did you, @mathmare , apply this fix? Did you build from sources or did you path your local installation? In any case, could...

In my typical uses cases i have multiple variables [a, b, c, ...] defined on the same coordinate grid. I then calculate some derived variable that indicates feasibility and plot...

@j08lue That sounds great! My use case fits perfectly with your concept of "pixel drilling". I didn't know that the feature had been discussed before. Regarding the different options, 1....