• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            Connecting Signals to QtScript Functions

            Posted by Kent on Tuesday, July 17, 2007 @ 19:31

            As we all know, connecting to the signals of a QObject from QtScript code is trivial; for example

            bossButton.clicked.connect(function() { desktop.showFakeSpreadSheet(); employee.grin(); } );
            

            However, what if you don’t intend to expose your QObject to script code? Let’s say you got this crazy idea, that you only intend for scripters to be able to code some script function (AKA “slot”) that you bring into your application, then you want to handle the actual signal-to-slot connections yourself, in C++ (god forbid!). What do you do then? Scream out in agony?

            Well, if you’re using the daily Qt snapshots, there’s actually no need to do so; a couple of days ago we added the necessary functionality. Let’s have a look at the obligatory, completely useless example. First, we have a fair amount of bland code (sorry about that) that sets up a widget with two buttons:

            #include <QtGui>
            #include <QtScript>
            int main(int argc, char **argv)
            {
            QApplication app(argc, argv);
            QWidget window;
            QVBoxLayout *vbox = new QVBoxLayout(&window);
            QPushButton *awakenButton = new QPushButton("Rise From Your Watery Grave");
            vbox->addWidget(awakenButton);
            QPushButton *exitButton = new QPushButton("Exit");
            vbox->addWidget(exitButton);
            

            Then we create our script engine, and a script object, and give the object a suitable name:

                QScriptEngine engine;
            QScriptValue object = engine.newObject();
            object.setProperty("name", QScriptValue(&engine, "Megatron"));
            

            We read our “slot” script function from a file:

                QFile file(":/slot.qs");
            file.open(QIODevice::ReadOnly);
            QScriptValue slot = engine.evaluate(file.readAll());
            file.close();
            

            Nothing out of the ordinary so far. But now we’re actually ready to do a signal-to-slot connection:

                qScriptConnect(awakenButton, SIGNAL(clicked()), object, slot);
            

            Wow. Just… Wow. How much easier, consistent and intuitive can it get? Both syntactically and semantically, it’s very similar to QObject::connect(). The main difference, of course, is that the last two arguments to qScriptConnect(), the receiver and the slot, are QtScript objects (one can be any type of object, the other must be a function object). When the QtScript “slot” function is executed in response to the signal, the receiver that you specified will act as the this-object. If you specify an invalid QScriptValue as the receiver, the this-object will be the interpreter’s Global Object; this even makes qScriptConnect() consistent with ECMAScript Function.prototype.call() and Function.prototype.apply(), for the purists who care about that stuff (hey, don’t look at me). There is of course also a qScriptDisconnect() function, which destroys a connection.

            Finally, demonstrating the principle of “Why do it the easy way when you can do it the hard way”, let’s round off main() by using qScriptConnect() to connect to QApplication::quit() as well:

                QScriptValue scriptApp = engine.newQObject(&app);
            qScriptConnect(exitButton, SIGNAL(clicked()), scriptApp, scriptApp.property("quit"));
            window.show();
            return app.exec();
            }
            

            Mmm, beautiful. Last, but not least, the QtScript function loaded from slot.qs, which is executed when the first button is clicked:

            return function() {
            var sender = __qt_sender__;
            sender.text = "YES! " + this.name + " is now alive and kicking!";
            sender.styleSheet = "background: lime";
            sender["clicked()"].disconnect(this, arguments.callee);
            sender.checkable = true;
            sender.toggled.connect(sender.hide);
            }
            

            First we use a QtScript extension to ECMAScript, __qt_sender__, to grab hold of the button that sent the signal (in general a dubious practice, if you ask me, whether it be script code or C++; but sometimes it’s just too tempting). We change the button’s text, give it a nice background color, then we break the connection that we established in C++ (arguments.callee to the rescue, as usual). Finally we do some more silly stuff, just to show that we can and aren’t afraid to do so.

            Oh yeah, in case you were wondering, you can also do a connect from C++ with the QtScript 4.3 API, by doing this:

            QScriptValue scriptButton = engine.newQObject(awakenButton);
            QScriptValue scriptSignal = scriptButton.property("clicked()");
            QScriptValueList args;
            args << object << slot;
            scriptSignal.property("connect").call(scriptSignal, args);
            

            It’s simple to create a convenience function based on this code, having arguments identical to qScriptConnect(). Way to go 4.3, counterattack!

            posted on 2007-10-07 00:20 清源游民 閱讀(2340) 評論(0)  編輯 收藏 引用 所屬分類: Qt
            <2007年10月>
            30123456
            78910111213
            14151617181920
            21222324252627
            28293031123
            45678910

            留言簿(35)

            隨筆分類(78)

            隨筆檔案(74)

            文章檔案(5)

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            国产亚洲色婷婷久久99精品91 | 国内精品久久久久伊人av| jizzjizz国产精品久久| 青青热久久综合网伊人| 一极黄色视频久久网站| 久久综合丁香激情久久| 国产精品中文久久久久久久| 久久精品免费观看| 无码精品久久久久久人妻中字| 国产精品视频久久| 伊人久久大香线焦AV综合影院 | 国产成人精品白浆久久69| 久久久久久噜噜精品免费直播| 久久久久久九九99精品| 久久久久亚洲AV成人网人人网站 | 亚洲日韩欧美一区久久久久我| 久久国产精品99国产精| 久久综合亚洲色一区二区三区 | 亚洲精品无码久久久久久| 久久亚洲色一区二区三区| 国产精品亚洲综合专区片高清久久久| 国产成人无码精品久久久性色| 久久男人中文字幕资源站| 精品人妻伦九区久久AAA片69 | 中文字幕无码久久精品青草| 国产高潮国产高潮久久久91| 国产精品美女久久久| 国产午夜精品久久久久免费视| 亚洲伊人久久大香线蕉综合图片| 老司机午夜网站国内精品久久久久久久久| 丰满少妇高潮惨叫久久久| 狠狠色丁香久久婷婷综合五月 | 久久久国产乱子伦精品作者| 亚洲中文字幕久久精品无码喷水| 人妻无码精品久久亚瑟影视| 亚洲欧美日韩中文久久| 久久久老熟女一区二区三区| 97久久综合精品久久久综合| 93精91精品国产综合久久香蕉| 久久综合九色综合精品| 久久亚洲电影|