QSystemScreenSaver etc

I just moved to Nokia QT SDK 1.0 (Windows 7) having previously been using a beta release.

My application was compiling and running OK with the beta for both the Simulator and Symbian release.

With the 1.0 Nokia QT SDK, the simulator version now builds/runs but the Symbian version fails to compile, with the following line highlighted in the UI:

#include <QSystemScreenSaver>

QSystermScreenSaver: no such file or directory, and also:

undefined reference to QtMobility::QSystemScreenSaver::QSystemScreenaver(QObject *);

at compile time.

I've also got my use of QTM_USE_NAMESPACE showing as an error when symbian is selected (this is also OK when the simulator is selected).

Can anyone advise how to fix this please ?

Thanks,
Rob

Hi, robnugent
Suppose the class [B]QSystemScreenSaver[/B] belongs to module or API [B]ABC[/B].

Then you have to add that module or API in the .pro file to add in the mobility.

Just like the below way :

[CODE] MOBILITY += [B]ABC[/B][/CODE]

Best regards,
RaHuL

Rahul,


Thanks for the reply.

I've got:

MOBILITY = location + systeminfo

Which was what I thought I needed, and what [B]worked fine[/B] with the beta of Nokia QT SDK.

Rob

[QUOTE=rahulvala;752659]Hi, robnugent
Suppose the class [B]QSystemScreenSaver[/B] belongs to module or API [B]ABC[/B].

Then you have to add that module or API in the .pro file to add in the mobility.

Just like the below way :

[CODE] MOBILITY += [B]ABC[/B][/CODE]

Best regards,
RaHuL[/QUOTE]

Where is the module/API of a given QtMobility class supposed to be documented? (Supposedly QSystemScreenSaver belongs to the SystemInformation API, but you can apparently only find this out by scanning all APIs for the class.)

Hi, danhicksbyron

[QUOTE]Where is the module/API of a given QtMobility class supposed to be documented? (Supposedly QSystemScreenSaver belongs to the SystemInformation API, but you can apparently only find this out by scanning all APIs for the class.)[/QUOTE]

I know that QSystemScreenSaver belongs to the [B]SystemInformation API[/B].
Though I gave him example using [B]ABC[/B].
So, that he can understand by himself.
Finally ,He got the solution.

[QUOTE]Rahul,


Thanks for the reply.

I've got:

MOBILITY = location + systeminfo

Which was what I thought I needed, and what worked fine with the beta of Nokia QT SDK.

Rob[/QUOTE]

Best regards,
RaHuL

Reread what he posted. He indicated that he already had "systeminfo".

And the QSystemScreenSaver doc page should say somewhere "systeminfo subcomponent" or some such. One very great general advantage of Qt over Symbian C++ is that you don't have to scan through the documentation tediously to dig out info such as this, but it seems that that advantage is being lost in the rush to add new function.

Rahul, Dan,

Thanks for the replies.

Just to be absolutely clear:

1) I've always had 'MOBILITY = location + systeminfo' in my project
2) Both Symbian and Simulator worked with the BETA of Nokia QT SDK
3) With Nokia QT SDK 1.0, the simulator build still works and runs
4) With Nokia QT SDK 1.0, the symbian build [B]fails[/B] with the originally reported symptom.

i.e. I still can't build my application.

Rob

Please read the solution at this bug report: [url]http://bugreports.qt.nokia.com/browse/QTSDK-98[/url]

TimsonC200,

Thanks for the reply - that seems to fix most of the problem - I can now compile and deploy again. (The syntax highlighting is still complaining in the QTCreator GUI, but that's no big deal and I'm happy to wait for an offical update to fix this).

Thanks again to all for you help,
Rob