How to put wait condition in Signal-Slot?

I am doin开发者_JS百科g one web related project. Recently I hit on this situation. This is just a stub

Class My_Class
{
public:
    My_Class();
    void start();
public slots():
    void after_Load_Function();
}

My_Class::My_Class()
{
    //Some initializations
    connect(WebPage,SIGNAL(finished()),this,SLOTS(after_Load_Function()));
}

void My_Class::start()
{
    WebPage->load();
}

void My_Class::after_Load_Function()
{
    //Do something with the finished WebPage
}

int main(int argc,char * argv[])
{
    //Some Qt things

    My_Class a;
    a.start();
}

"WebPage" emits the signal "finished" when it loaded fully. Now the problem is before the "webPage" got loaded the "start" is returning. Thereby the control reaches the "main". So, now the control should return from "start" only after "after_Load_Function" finishes it's job. Thereby I want the below sequence,

1. main creates the My_Class object A.
2. main calls "start" from A.
3. start calls load from "WebPage" and it waits untill the "WebPage" emits "finished", and that emit in turn calls the "after_Load_Function", and "after_Load_Function"

   finishes it's job.

4. now, the "start" returns
5. main returns

But, I don't know how to make this kind of wait condition. How can I go about it?

---

You can do this by running a local event loop, letting the components process network income and load the page. When they emit the signal, you execute a slot on the event loop to quit it.

void My_Class::start()
{
    QEventLoop qel;
    QObject::connect(WebPage, SIGNAL(finished()), &qel, SLOT(quit()));

    WebPage->load();
    qel.exec();
}

I've been using this before and it works fine. I don't advice to use this too often though, because it will process events, including those that the caller of start might not be expecting to be processed during the call to start, so you need to document this to its callers. You can prevent the processing of some events by passing certain flags to QEventLoop::exec, like preventing to process user interface events.

---

You should never wait in UI code. You need to break your "main" function into pieces so the later part can be executed separately.

---

Use condition variables thats what they are used for. You can make threads wait on a condition variable and proceed when notified.

---

The WebPage->load() method is asynchronous, meaning that it runs immediately, not when the loading is complete. The operation runs in the background while you go to do other things.

This is considered a good thing, as it enables your app to be more responsive and get more done. For example, if your app has a GUI, you could update the GUI with some sort of animation that indicates that the web page is being retrieved.

If you prefer a model in which the application blocks until the page is fully loaded, then consider making this change:

void My_Class::start()
{
    WebPage->load();
    while (!WebPage->isLoaded())
        Sleep(1);
    after_Load_Function();
}

Notes:

• the Sleep function will work on Windows. If you are on a Unix OS you can use usleep.
• since this function will effectively block until the web page is loaded, there is no reason to use the signal from the web page object, you can just simply call your handler after the wait completes, as this will make your handler run in the same thread.
• doing this is really bad practice. You may get away with it if your program is command line and has no GUI and/or event loop, but you should consider a better design for your app where the loading of web pages does not block the whole app.