EventCatcher widget - use setPointerCapture?

[BurningTreeC]

We could use setPointerCapture (https://developer.mozilla.org/en-US/docs/Web/API/Element/setPointerCapture) as an additional parameter for the eventcatcher widget.

I would like to discuss this and the benefits it would give us

[Jermolene]

Hi @BurningTreeC good idea. The challenge is that the eventcatcher widget might get destroyed and recreated when a parent widget is refreshed. Presumably we'd have to track the current capturing element rather like the work you've done on tracking the focussed element.

[Jermolene]

Hi @BurningTreeC very interesting! Does this still use the dynamic stylesheet technique we saw before?

[BurningTreeC]

No @Jermolene , this uses inline styles

[Jermolene]

Great, let's see it!

[BurningTreeC]

I'm a bit shy about showing this macro 😁 ... it only works if we don't change the width of the container and if we don't change the amount of columns. If we change those, we need to delete the state tiddler.

I'm still working on this macro and the handling for when the width and the amount of columns changes is missing.

But I guess some more pairs of eyes on the code would help

[Jermolene]

I'm a bit shy about showing this macro 😁 ... it only works if we don't change the width of the container and if we don't change the amount of columns. If we change those, we need to delete the state tiddler.

I'm still working on this macro and the handling for when the width and the amount of columns changes is missing.

But I guess some more pairs of eyes on the code would help

Inevitably, I'm always very focussed on the question of "how do we get this into the core"; an alternative approach would be to work on getting it packaged up for users as it is so that you can explore with them how much these limitations matter in practice...