background process/thread
| Wed, 2008-05-28 20:47 | |
|
Hi. If I make it a console app, and a call event happened, it will move from the console view to the 'ringing call' view. Does this kill my AO? If it does, the call won't be answered. If I make it a GUI app, start the AO with a button click, and destruct the GUI view, will my AO still be alive when the phone is ringing? Or maybe a small dll to work with the ETEL server? Help.. |
|







Forum posts: 59
small thought here,
you can create a thread or server and start it at the phone bootup and wait for the call event.
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
How can I start a sis/exe/dll at phone boot?
Forum posts: 59
Actually I have seen starting some servers on bootup. But I have to findout how to do that. I am sure you can do it. because at startup lots of symbian server is getting started in the background.
I will try and update.
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
Thanks a bunch. I just found some info on start-on-boot API.. How do I get it?
Forum posts: 59
can you please share that?
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
http://www.newlc.com/article.php3?id_article=451
Forum posts: 59
Looks good. I will try this. Thanks a ton
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
Another related question:
Does a CActive memeber variable of a Uikon framekwork stay active when the view changes to embedded OS ?
Forum posts: 59
The question is quite unclear. Anyways as long as CActive object alive and accessible, you can get member variables also.
What do you exactly mean by switching to embedded OS?
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 1197
n_ape:
Symbian is a modern multithreaded multitasking operating system.
Each application runs in its own process, and what is currently showing on the screen is totally irrelevant for what processes are currently running.
Typically you have at any time a bunch of them running, from OS services to different phone services to pre-installed apps like main menu and calender and phonebook, to add-on installed applications.
Your application will run for as long as its process is kept alive, it doesn't matter if it currently shows something on the screen or not.
You should think of it a bit more like when programming for a normal PC, and not so much traditional embedded programming.
Forum posts: 17
alh, what is the lowest entry point of an AO? Do I need to hard code it into my own thread or process in order for it to launch?
Forum posts: 59
If I am correct, Thread / Process has entry point function. And it should be implemented and passed to RProcess::create or RThread::Create function.
AO, is part of a thread. Active Scheduler is responsible for managing each active object.
There are some basic rules for creating / starting AO & there should be some standard functions need to be implemented. you can refer some pages like "how to start AO" from SDK documentation
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
Do I HAVE to manually start a new process/thread if not using the app framework? Or does the OS take a E32main() and auto manages it into the stack?
Forum posts: 59
I am not quite sure about that. You can manually start your thread by calling RThread::Resume() after creating it.
you have an option to make ur process start at bootup. (I am still searching how to do that)
"Or does the OS take a E32main() and auto manges it into the stack?" - No idea in this.
Started my Journey in Symbian - http://celluleus.blogspot.com/
Forum posts: 17
It's OK I know I'm difficult