Symbian Publish & subscribe: persIstent storage?

[mainguet]

Hi,

I'm using Qt SDK 1.1 beta to develop on Symbian. I wanted to use Publish & Subscribe to store my app settings. I manage to do it by using RProperty type of store but in this case my data are lost after a reboot. So I though of using CRepository instead but no data are stored at all in this case, not even between reboots.

My qcrml file is like this:

<?xml version="1.0" encoding="UTF-8"?>
<repository target="CRepository" uidValue="0xE3397C00">
<key ref="/test/login" int="0x1" type="string"/>
<key ref="/test/password" int="0x2" type="string"/>
<key ref="/test/server" int="0x3" type="string"/>
<key ref="/test/port" int="0x4" type="string"/>
<key ref="/test/instance" int="0x5" type="string"/>
</repository>

The way I access the store is exactly the same way that works with RProperty. Should I change something to use CRepository? I've added ReadDeviceData and WriteDeviceData, just in case.

And if that's not the correct way, how to easily store config data on Symbian?

Thanks for your help

[danhicksbyron]

QSettings, perhaps?

[mainguet]

Yes, I can try. I thought this was only for Windows, MacOS and Unix but I can try...
My problem is also that I wanted to use Pub&Sub for IPC, as those values can be set by one UI and read by a server...

Thanks

[ltomuta]

I really don't see how the Central Repository scheme would work as documented in the Mobility API. Even for Symbian C++ developers the CRs are largely out of reach as the framework wasn't really designed for every application to use it. The installation process for new CRs is complicated and the definition process not documented, at least not in the SDK. Even the write methods of the CRepository API were classified as "internal technology".

Bug report created at QTMOBILITY-1437

By default QSettings stores its data in an unprotected location so both processes should be able to access it.

[mainguet]

Thanks! That clarifies things!