Simon Hausmann

@ogoffart: Does that sound correct to you? A `wheel-event` in Slint that takes a `WheelEvent` struct as parameter, with `position_x`, `position_y`, `delta_x` and `delta_y`?

That looks promising, I'll keep an eye on that. Thanks for the pointer!

Done :). Thanks for the feedback and the checklist!

That’s excellent. Thank you for the update (and your work on AccessKit)!

A graphical tool / editor has been on our radar since the beginning. However we haven't created a ticket here yet for tracking that, as we've so far been busy...

> In my opinion, a good goal for a new GUI editor would be [wxFormBuilder](https://github.com/wxFormBuilder/wxFormBuilder/). SixtyFPS could easily use that as a guideline or benchmark: > >  > >...

A new workaround has surfaced: Add this to your `Cargo.toml` to compile the macro crate in release and thus reduce the amount of symbols that require an ordinal each: ```toml...

Another option would be to use one shared offscreen canvas for all webgl rendering and transfer the result onto each 2d target canvas. This comes at the expense of resizing...

Another possibly less effort approach would be annotate some of the canvas elements with a data tag as "static" (as opposed to "interactive") and then discard the context after rendering...

Another possibility is to virtualise the webgl calls, that's implementing the sharing in JS instead of in Rust: https://github.com/greggman/virtual-webgl