Re: [Interest] QJSValue as parameter to Q_INVOKABLE

2014-05-01 Thread Gav Wood
Yeah - Q_OBJECT makes no difference. I should have noted that I'm wanting to integrate into the Javascript behind the QtWebkit stuff. So notably a number of things work fine with Qt/JS integration for QtQuick (as yours does) and not for QtWebkit: Padding registered meta types around as values in

Re: [Interest] QJSValue as parameter to Q_INVOKABLE

2014-04-29 Thread Gunnar Sletta
Your QObject needs to have Q_OBJECT in it, but aside from that that, it looks sane enough. I've been using the same approach in https://codereview.qt-project.org/#change,72338 and it works like a charm there. cheers, Gunnar On 29 Apr 2014, at 16:03, Gav Wood wrote: > Hi, > > I'd like to ex

[Interest] QJSValue as parameter to Q_INVOKABLE

2014-04-29 Thread Gav Wood
Hi, I'd like to expose an API within a QJSEngine JavaScript environment for an asynchronous callback. Thus I want to expose a method "regCallback": foo.regCallback(function() { alert("Hello"); }) and allow C++ to call that function at some later point. The function is exposed as a QJSValue, thu