Capturing dialling event with application on background

[ishan.malviya]

can we capture dialling event in our application running in background

[aamitgupta]

what u want, no call dialog box comes during call.

[ishan.malviya]

that too, but the main intention is getting the number being dialled...... if we can stop the dialling box that would be great too

[kiran10182]

that too, but the main intention is getting the number being dialled...... if we can stop the dialling box that would be great too

See this:
http://wiki.forum.nokia.com/index.ph...m_numeric_keys

Kiran.

[aamitgupta]

in which OS u are working. For hiding call dialog box, draw FBS bitmap of screen that capture before calling, draw it many times after call connected, gets dialled number by Ctelephony.

[kiran10182]

in which OS u are working. For hiding call dialog box, draw FBS bitmap of screen that capture before calling, draw it many times after call connected, gets dialled number by Ctelephony.

What do you want to suggest actually? I guess you are referring to hiding a call box with respect to incoming call event, aren't you?
But the originator is saying about capturing numeric keys so that he can stop the caller from calling.

Please let me know if i have understood anything wrong.

Kiran.

[ishan.malviya]

our basic intention is to get all calls made through our application.... so basically we want the number dialled by the user and connect the call through our application...

we have been successful in....

letting the user dial the number, then get the number and cut the call . but this is not the right approach...

one way can be listen for the dial key, on key press event(dial) get the number to be dialled even before the call is connected and dial through our application

[ishan.malviya]

is this possible

[morost]

See this:
http://wiki.forum.nokia.com/index.ph...m_numeric_keys

Kiran.

I'm also working in something similar to ishan application.
I read the linked page but I don't understand some things.

with RWindowGroup::CaptureKey() in fact is possible to capture numeric keys, with my application I'm able to capture keys that the user insert in idle screen when He would dial a call.
The keys are also properly handled by phone application, because after "observe" them I send the keys with SendEventToWindowGroup() function and when the user press the green key the call starts...

Then I don't understand if this "Know Issue" is a bug segnalation (I think in this case not really true..) or a behaviour that developers must respect... in other words.. my application will be Signed if I don't respect this "Know Issues" or not ?

thanks.

Ste

[kiran10182]

... my application will be Signed if I don't respect this "Know Issues" or not ?

thanks.

Ste

From my personal experience, i would say that it should not cause you a problem with Symbian signed. And i must admit i have not gone through very carefully with the new test criteria. So just have double check all the points before moving forward.

All the best.
Kiran.

[antonypr]

Then I don't understand if this "Know Issue" is a bug segnalation (I think in this case not really true..) or a behaviour that developers must respect... in other words.. my application will be Signed if I don't respect this "Know Issues" or not ?

I had the same question with my application, Screenshot app (www.antonypranata.com/screenshot) quite some time ago.

As far as I know, the "Known Issue" at the Wiki page describes unwanted behavior if you capture numeric keys and ***do not*** re-send the key events to the phone application using SendEventToWindowGroup(). It will behave very weird.

So far, I've been using SendEventToWindowGroup() in my application to capture numeric keys and found no problem. It also passes Symbian Signed. My suggestion is try to test your application with other applications (not only phone application) and see. For example, test in Messaging or Office application because those applications require numeric keys.

[morost]

thanks for the answers !


Ste