Liu BoFan

Solution B +1

I hope make `sciter::Element` multi thread friendly first, using working thread update dom is very common way to avoid blocking ui thread.

``` macro_rules! MAKE_HANDLE { ($name:ident, $inner:ident) => { #[repr(C)] pub struct $inner { _unused: usize } pub type $name = *mut $inner; }; } ... MAKE_HANDLE!(HELEMENT, _HELEMENT); ... pub struct...

I dont fully understand what you said ` brings the window to the foreground`, Can you explain more detail about what you are proposing?

Very interesting idea. I will do some research on this, although I probably would not add this kind of complex feature to this simple crate.

One solution I can imagine is use unix domain socket inform another instance.

`instance:node_cpu:ratio` metric's time window is 5m. ```promql sum(rate(node_cpu_seconds_total{mode!="idle",mode!="iowait",mode!="steal"}[5m])) WITHOUT (cpu, mode) / ON(instance) GROUP_LEFT() count(sum(node_cpu_seconds_total) BY (instance, cpu)) BY (instance) ``` https://github.com/prometheus-operator/kube-prometheus/blob/7a3879ba49bfe8df5eec03847fe5bcd2d4094c73/jsonnet/kube-prometheus/components/mixin/rules/node-rules.libsonnet#L20

Same problem. I called `_flutterLineLogin.startLogin(_onLoginSuccess, _onLoginError);` in a bloc mapEventToState function then the app crashed with same error message. ```bash ➜ ~ flutter doctor Doctor summary (to see all details,...

@hitshydev Thanks, I already tried the flutter_line_sdk, it works well with v1.7.8+hotfix.4.