How to open a url using symbian browser??

Hi,

I want to open a url using the native browser application. Is that possible from the symbian application's code? I came to know about [B]CBrCtlInterface [/B]class but could not find
any example for this.

can somebody give some pointers?

What about checking wiki: [url]http://www.developer.nokia.com/Community/Wiki/How_to_Launch_Browser_in_3rd_edition[/url] should still work just fine.

Yes yucaa it does. Thanks.

But when i try to open this with a default url, it fails saying [I]unable to perform operation -26000[/I]
couldn't find what that means.

What excatly you try doing ?
And how ?

Anyway I would just use it with "4+ <Space>+<Url>" option, also you should remember to add SwEvent capability to your app.

I want exactly what you suggested. That already has "4+space" + method takes url. I also added SwEvent capability. This is just fine but when i am opening a url through browser, after winsock connect, it s throwing this error
Web:
Unable to perform operation (-26000)

but if i try to explicitly type the url when the browser is opened, it works. Thats not what i want. Application has to pass url while launching the browser.

Basically it has worked just fine , so how are you trying to use it ? And can you show what kind of string you are giving iin there ?

I have not changed anything in the method.
I am calling that method something like this:

[I]LaunchBrowserL(_L("http://www.google.com"));[/I]

This is all fine except that error.

Trying on a real device or on emulator? with : [B][I]winsock connect, it s throwing this error [/I][/B], seems like emulator

[QUOTE=vineet.jain;911292]Trying on a real device or on emulator? with : [B][I]winsock connect, it s throwing this error [/I][/B], seems like emulator[/QUOTE]

thanks, somehow missed that one..

On both. On emulator it gives that panic and on real device, the browser opens and crashes very quickly and focus comes back to application.

Never seen that behaviour. Anyway, can you check that the device has latest firmware, and then you could check the panic ode for the crash. Also you could check whether it is device problem, by trying it in the RDA as well.