Do you want to run your process all the time until its been closed explicitly by an applicaiton.
Its simple to do..
DO NOT STOP YOUR ACTIVE SCHEDULER UNTIL YOU KILL YOUR PROCESS !!!
Implement your Decrementsessions function as follows,
{
iSessionCount--;
if ( aShutDown )
{
CActiveScheduler::Stop();
}
}
To let your application to use the full screen, please add the following line in your Appview class.
SetExtentToWholeScreen();
This is a public API in ccoecontrol. So, any CCoeControl class can use this. After adding this line, your application will not be having any control pane or status pane.
Note: This code is tested on S60 5th edition and in portrait mode
1. Install needed IDE and SDKs
Make sure you have the following installed:
* Carbide.c++ v2.0.0 or higher
* S60 Platform SDK 3rd Edition FP1 or higher
* Open C/C++ for S60 3rd Edition (automatically included in 3.2 and higher)
These instructions assume the above tools are installed and that the enviroment variables for your compiler are set correctly.
Note: Users of S60 Platform SDK 3rd Edition FP1 also need special updates. The update can be found here.
Note: The wsini.ini provided with the S60 Platform SDK 5th Edition v0.9 needs to be updated for correct font rendering in the emulator. The update can be found here.
2. Install Qt
Uncompress the package into the directory you want Qt installed, e.g. C:\Qt\4.5.0-garden.
Note: Qt must be installed on the same drive as the S60 SDK you are using, and the install path must not contain any spaces.
3. Environment variables
In order to build and use Qt, the PATH environment variable needs to be extended:
PATH - to locate qmake, moc and other Qt tools
This is done by adding c:\Qt\4.5.0-garden\bin to the PATH variable.
On Windows the PATH can be extended by navigating to "Control Panel->System->Advanced->Environment variables".
In addition, you must configure the environment for use with the S60 emulator. This is done by locating the Carbide.c++ submenu on the Start menu, and choosing "Configure environment for WINSCW command line".
4. Configure Qt
To configure Qt for S60, do:
cd \Qt\4.5.0-garden
configure -platform win32-mwc -xplatform symbian-abld
For other options, type configure -help to get a list of all available options.
5. Build Qt
The Qt libraries comes pre-built for real devices. If you are using a 3.x S60 SDK, install qts60binaries\3.x\qtlibs-4.5.0-garden.exe into the S60 SDK root directory. For example: C:\Symbian\9.2\S60_3rd_FP1_2\ If you are using a 5.0 S60 SDK, install qts60binaries\5.0\qtlibs-4.5.0-garden.exe into the S60 SDK root directory. For example: C:\S60\devices\S60_5th_Edition_SDK_v0.9\
To build Qt for the emulator, type:
make debug-winscw
Congratulations, Qt is now ready to use.
6. Running Qt demos
We've included a subset of the Qt demos in this package for you to try out. An excellent starting point is the "fluidlauncher" demo. To run the demo on a real device, you first have to install the Qt libraries on the device. For 3.x devices install qts60binaries\3.x\qt_libs_armv5_udeb.sisx For 5.0 devices install qts60binaries\5.0\qt_libs_armv5_udeb.sisx included in this package to the device. Then type:
cd examples
make debug-gcce
cd ..\demos
make debug-gcce
cd embedded\fluidlauncher
createpackage -i fluidlauncher_gcce_udeb.pkg
This will create a self-signed fluidlauncher_gcce_udeb.sisx and install it to your device.
Note: You can specify your own certificate and key files as additional parameters to createpackage if default ones are not suitable.
To run the demos on the emulator simply run:
make run
Or, if you need to supply arguments to the program, navigate to %EPOCROOT%\Epoc32\release\winscw\udeb\ and start any of the Qt demos located there, for example:
wiggly.exe -small-screen
For more information about building and running Qt programs on S60, see S60 - Introduction to using Qt.
We hope you will enjoy using Qt.
Carbide.c++ 2.0 does not automatically locate your Qt installation so you need to tell it where Qt is installed. You can do this through the Carbide.c++ preferences. From the main menu choose Window > Preferences. In the preferences dialog, choose Qt. Then clickAdd.... A new dialog will open and there you can enter the Qt version name, the bin path and the include path. See the following image for an example.
HookLogger
It is one of the most time consuming task for developers to find memory leaks in their code. If your application happens to panic on exit with some memory leak, then sometimes it is a hard work to find the wrong piece of code with code analysis. HookLogger is a great emulator tool by Symbian that helps finding the leak fast.
Install
*Read carefully*
* Latest version can be download from nokia website also
* Install HookLogger to path *without* spaces (c:\s60\hooklogger). Hooklogger must be installed to the same drive as SDK.
* In DOS prompt, do following:
** cd \utils\hooklogger
** type SetupHooks.cmd devicename
devicename can be found, by typing devices in the command prompt
My device is S60_5th_Edition_SDK_v0.9:com.nokia.s60
* On successful hooklogger setup you will get the following information in the command prompt
Setting up hooks in "C:\S60\devices\S60_5th_Edition_SDK_v0.9\epoc32\release\WINSCW\UDEB"
1 file(s) copied.
Setup euser.dll to load EUserParasite_EKA2.dll, original preserved as euser.orig.dll.
Run SetupHooks with --r to restore it
* Once you are done with the usage of hooklogger you just restore your euser.dll by typing
SetupHooks.cmd --r devicename
Running the Program with hooklogger
* Open the hooklogger
* Select filters tab
* click "Browse for exe"
* select the application to be monitored
* Make sure you have selected "include only checked"
* Now launch your application
* Once the emulator is launched you can see the hooklogger heading is changed to your application executable's directory
* Run your application, do some operation and close it
* Now in hook logger, you can select heap tab.
* Say list all and it shows all the heap allocations
* If you double click on any of the entry it shows the callstack of that allocation
* This will be useful to find out the memory leaks (alloc panics)
