Internet connection with Qt for symbian
I am creating a Qt Symbian application and need an internet connection. In some way, I have to let the user select the connection when the application starts. I could use Qt Mobility to make it work, but when Nokia approves, I won't publish my app on the Ovi Store. Since Qt Mobility is not included in Qt 4.6, there may be a problem publishing my application later. So for this reason, I'm going to use my own APIs.
The idea is to use: qt_SetDefaultIap () to establish a connection at startup. I looked at it to see what it does. If I have two connections that the app can use, one with WIFI and one over mobile internet, which will qt_SetDefaultIap () select? And can I somehow with the native api force the user to select the connection on startup? (It seems that qt_SetDefaultIap just set up the default connection on its own, no user selection)
Thanks!
a source to share
Qt 4.7 is now released, and while not all Mobility APIs have turned it into core, QNetworkSession has.
Mrbiggerm: It looks like you found the sym_iap_util.h file that is included in the QFtp sample code in the Qt SDK. Instead of calling qt_SetDefaultIap (), try calling qt_OfferIapDialog () and passing its return value to qt_SetDefaultIapName (). This should do what you want it to do. (Although a bit hacky, it's often the preferred option as it introduces the S60's own UI rather than letting you implement your own hotspot list.)
a source to share
Do you expect to finish your program before Qt 4.7 is released (I don't know the exact release date, but I would estimate it around July), which AFAIK will contain Qt Mobility?
If the answer is no, don't worry about issue issues, use your own QtMobility build for development, wait 4.7 and don't worry about issue issues.
If so, what is stopping you from deploying your program with a custom QtMobility assembly? Internally, it uses the same native API calls that you want to use, not some super secret Nokia API, so there shouldn't be any trouble checking the code (in fact, there will probably be less trouble since you don't have will be able to inject code covered by the QtMobility libraries).
a source to share