Re: internal loop

guda — Mon, 28 Aug 2006 11:24:54 +0200

thanks a lot.

Re: internal loop

Paradroid — Mon, 28 Aug 2006 00:21:52 +0200

Active objects: the "loop" is actually the thread's active scheduler, and the dialog just implements a RunL that does some small task (in wait dialog's case, update the animation I would presume) and then re-schedules itself to run. This way, the phone remains responsive because the scheduler can choose other tasks to execute also (e.g. key events, other animations on the background, etc.).

Now, if you're asking how you can "block" the execution yourself so that you can implement this, it's done with CActiveSchedulerWait class (can't remember which header it's in, sorry, try to search for it). The code goes something like this:

Code:

class CSomeClass : public CBase {
// This is your dialog class or whatever
private:
CActiveSchedulerWait iWait; // This is a C class so it can't be on stack,
// But it can be a member variable of another C-class.
};

// Actual code:

iWait.Wait; // This instantiates another scheduler loop.

// Somewhere else in the code, (e.g. in OkToExitL or ProcessCommandL):

iWait.AsyncStop();

// Execution continues, but once this active objects RunL finishes
// it returns to the original loop.

Ok, sorry about the uninformative example. I'm just typing it from memory.

internal loop

guda — Sun, 27 Aug 2006 23:34:22 +0200

NewLC - internal loop - Comments

Re: internal loop

Re: internal loop

internal loop