pravic

```rust dispatch_script_call! { fn process_window(Value) ; } ``` Try this. Basically, leave the window as a Sciter value. What do you want to do with it in general? `sciter::Window` is...

Well, they use `feature(abi_thiscall)` and compile it on nightly only. Thanks for the heads up!

Haven't tried it yet. Sciter has become thread-safe not so long ago (since 3.3.1.9) and had issues at the beginning with it. Okay, I will take a look. Or you...

Partly true, because UI thread can be blocked by Sciter itself (that's how thread safe API calls are implemented). But not always, of course. As for `Send+Sync` candidates - it...

There we go: #18 for the `Element`.

And for the `Value`. However, Value API is not thread safe, so it can be marked as `Send` only, but not as `Sync`. Since [0.4.21](../releases/tag/0.4.21) version.

Hmm. You should **isolate** value [received from UI](https://sciter.com/forums/topic/about-thread-safety-guaranties/) before passing it to another thread. I am not sure how to make this guarantee in Rust. May be via some handle/wrapper,...

`sciter::SafeValue`? :)

> May be via some handle/wrapper This. Also it comes with `Deref`, so it's quite easy to use: ```rust let v = Value::map(); let mut v = v.isolate(); std::thread::spawn(move ||...

It's not so easy. It is messy, actually. Part of the Value API is thread safe (e.g. function calls), the rest of it **is not** (e.g. map/array access). Moreover, a...