Rom Grk

> Maybe it's feasible to release a major version soon? We're still pre-1.0, so we can do anything we want :smile: Joke aside, yes, and it would be nice to...

I'd be happy to have another contributor ^^ AFAICT, all the changes that would be needed would be in [value.cc](https://github.com/romgrk/node-gtk/blob/master/src/value.cc), which is where we do all our conversions, plus updating...

Thanks for the report, I had already seen a few of these errors but wasn't sure where they were coming from. I'll investigate what's going on.

Got it. We can probably skip the issue by using `malloc` directly rather than `g_slice_alloc`.

Update on this, it seems that we had already migrated away from `g_slice_alloc` to `malloc`. https://github.com/romgrk/node-gtk/blob/c3dc55d7a6242801187f83fc068c1f74d34fead8/src/boxed.cc#L186 This is bad news because it means the bug is upstream. After some debugging,...

Haven't had time to look into this yet, but I'll comment here for your information. This use-case is something that should be supported. Last time I played with the event...

Yes that's something I had already noticed some time ago. I've done some work in [#265](https://github.com/romgrk/node-gtk/pull/265/files#diff-7c1522eda93be29b10603eb3eb690c75ac2c85aac10adb7d952270e557d7dfdbR21-R42) to try to fix the issue, but I haven't had time to test all...

I think we could get away with just node but separate threads. IIUC, the problem is that Qt absolutely wants to be in the main thread, therefore it cannot be...

I also prefer to avoid a forked nodejs. Don't have anything to add regarding solution to this issue at the moment, any solution needs research before commenting more.

That's an interesting one. I'd rather try to understand and fix it first, if there is a technical reason for why it can't be fixed I'll include a mention in...