Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Well, i got this error from nstl:

"On says:
"Error #1: If the user selects "Exit" or presses the "Clear" key at the main
menu, the application returns to the phone's main screen instead of
returning to the Application/Brew Manager. (Test Case 3.1.6.3)"
"

Well... what i do is returning false when i get the AVT_CLR..

Any tips?

/kUfa

I _think_ if you call:
ISHELL_CloseApplet(pShell, FALSE);
it will return to the app manager, and
ISHELL_CloseApplet(pShell, TRUE);
will return to the phone's main screen.
try it and see.
-Tyndal

I _think_ if you call:
ISHELL_CloseApplet(pShell, FALSE);
it will return to the app manager, and
ISHELL_CloseApplet(pShell, TRUE);
will return to the phone's main screen.
try it and see.
-Tyndal

Thx, will try :)
/kUfa

Thx, will try :)
/kUfa

Well, i checked my code, i do not use ISHELL_CloseApplet when my app exits when it gets a AVT_CLR (i return FALSE in the event)...
/kUfa

Well, i checked my code, i do not use ISHELL_CloseApplet when my app exits when it gets a AVT_CLR (i return FALSE in the event)...
/kUfa

Right, i think that is the default behaviour if you dont handle AVK_CLR, i was suggesting how you might be able to get the "desired" behaviour to occur by using CloseApplet.
Did this cause you to fail testing, or was it just marked as a "passed with notes" item?
I think some apps ive developed before exit to the main phone screen and i dont think i was failed/marked off for it.. but the person that submitted the app might have explictly mentioned the behavior in the test doc (i am not the one who handled the final testing/submission to NTSL)
-Tyndal

Right, i think that is the default behaviour if you dont handle AVK_CLR, i was suggesting how you might be able to get the "desired" behaviour to occur by using CloseApplet.
Did this cause you to fail testing, or was it just marked as a "passed with notes" item?
I think some apps ive developed before exit to the main phone screen and i dont think i was failed/marked off for it.. but the person that submitted the app might have explictly mentioned the behavior in the test doc (i am not the one who handled the final testing/submission to NTSL)
-Tyndal

We had a problem like this on the LG6000, the problem was the LG6000 does the same thing on key_up and on Key_down in the get it now menu. And our game processed input on key down. So we got the clear key on key down, close the app and go back to the get it now menu, Then the key up gets processed by the phone and does another clear, sending it back to the main phone menu.

We had a problem like this on the LG6000, the problem was the LG6000 does the same thing on key_up and on Key_down in the get it now menu. And our game processed input on key down. So we got the clear key on key down, close the app and go back to the get it now menu, Then the key up gets processed by the phone and does another clear, sending it back to the main phone menu.

Gugu,
You know there is 3 different key events, EVT_KEY_PRESS, EVT_KEY_RELEASE, and EVT_KEY, right? Unless you need to do something that requires holding down a key or something, you probably only need to handle EVT_KEY, especially for things like AVK_CLR.
The vx6000 may have a problem with it as you say, but i dont have one on hand to check it out. I just wanted to make sure you are aware of EVT_KEY.
-Tyndal

Gugu,
You know there is 3 different key events, EVT_KEY_PRESS, EVT_KEY_RELEASE, and EVT_KEY, right? Unless you need to do something that requires holding down a key or something, you probably only need to handle EVT_KEY, especially for things like AVK_CLR.
The vx6000 may have a problem with it as you say, but i dont have one on hand to check it out. I just wanted to make sure you are aware of EVT_KEY.
-Tyndal

We had this problem on a couple of handsets, including the VX6000 and the KX414.
tyndal is right that it has to do with a subtlty with EVT_KEY and EVT_KEY_PRESS. BREW generates both, first EVT_KEY_PRESS then EVT_KEY. On some devices, if the application closes as a result of EVT_KEY_PRESS then the EVT_KEY which is "dangling" gets passed to the Get It Now menu. If that key was AVK_CLR then the Get It Now menu will exit back to the phone's root, and if it was AVK_SELECT then (typically) the Shopping Cart will launch.
So the trick is to never exit in EVT_KEY_PRESS, particularly if the key was AVK_SELECT or AVK_CLEAR.
-Jesse

We had this problem on a couple of handsets, including the VX6000 and the KX414.
tyndal is right that it has to do with a subtlty with EVT_KEY and EVT_KEY_PRESS. BREW generates both, first EVT_KEY_PRESS then EVT_KEY. On some devices, if the application closes as a result of EVT_KEY_PRESS then the EVT_KEY which is "dangling" gets passed to the Get It Now menu. If that key was AVK_CLR then the Get It Now menu will exit back to the phone's root, and if it was AVK_SELECT then (typically) the Shopping Cart will launch.
So the trick is to never exit in EVT_KEY_PRESS, particularly if the key was AVK_SELECT or AVK_CLEAR.
-Jesse