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

Developer

Forums

Forums:

I am seeing totally different behaviour after a call to ISHELL_Prompt() on the simulator to on the hardware.

 

If ISHELL_Prompt() is called with a timeout value of 0 then:

- on the simulator the dialog is NEVER displayed and an EVT_COMMAND event is immediately received with a wParam value that IS NOT that of the specified default button (it is the first button in the button array).

 

- however on hardware the dialog IS displayed and behaves correctly.

 

If ISHELL_Prompt() is called with a timeout value of > 0 then:

- on the simulator the dialog IS STILL NOT displayed and an EVT_COMMAND event is immediately received. But this time the wParam value IS that of the specified default button.

- However on hardware things work as expected.

 

Questions - why is the behaviour different on the simulator to the hardware, why is the behaviour different depending upon the timeout value.

These differences are very irritating and really hinder development, it effectively means the simulator cannot be used.

Is there an inherent problem with the simulator, or some problem with my code which is causing these differences? If so what could the problem be?

Whcih simulator you tried? I was able to display dialog on Brew MP 1.0.3.692 candy bar simulator in both cases - timeout is 0 or > 0.

Whcih simulator you tried? I was able to display dialog on Brew MP 1.0.3.692 candy bar simulator in both cases - timeout is 0 or > 0.

Hello, on Brew MP Candy Bar 1.0.2.549.1.
 

 
 

If in general dialogs behave fine on the simulator, any speculation why I am seeing differing behaviour on the simulator to hardware? Could the architecture of my program somehow affect it?
 

 
 

The code to invoke the dialog is:
 

 
boolean Utils::MessageBox(IShell* piShell,
WString &Title, WString &Text,
const uint16 * pBtnIDs, uint16 defBtn, uint32 dwTimeout)
{
String fileName = pMVCCore.GetResourceFileName().toCharArray();
AEEPromptInfo pi = {
fileName.toCharArray(),
Title.toCharArray(),
Text.toCharArray(),
0,
0,
defBtn, // Command to send when CLR is hit (default is first entry)
pBtnIDs, // const uint16 * pBtnIDs;
ST_CENTERTITLE | ST_UNDERLINE,
AEE_FONT_BOLD,
AEE_FONT_NORMAL,
dwTimeout
};

return ISHELL_Prompt(piShell, &pi);

Hello, on Brew MP Candy Bar 1.0.2.549.1.
 

 
 

If in general dialogs behave fine on the simulator, any speculation why I am seeing differing behaviour on the simulator to hardware? Could the architecture of my program somehow affect it?
 

 
 

The code to invoke the dialog is:
 

 
boolean Utils::MessageBox(IShell* piShell,
WString &Title, WString &Text,
const uint16 * pBtnIDs, uint16 defBtn, uint32 dwTimeout)
{
String fileName = pMVCCore.GetResourceFileName().toCharArray();
AEEPromptInfo pi = {
fileName.toCharArray(),
Title.toCharArray(),
Text.toCharArray(),
0,
0,
defBtn, // Command to send when CLR is hit (default is first entry)
pBtnIDs, // const uint16 * pBtnIDs;
ST_CENTERTITLE | ST_UNDERLINE,
AEE_FONT_BOLD,
AEE_FONT_NORMAL,
dwTimeout
};

return ISHELL_Prompt(piShell, &pi);

I tried on that simulator as well but didn't see any issues. Here is what I did:
uint16 wButtons[2] = {IDS_STRING_1001, IDS_STRING_1001};
AEEPromptInfo pi = { STATICWGTAPP_RES_FILE,
L"Test prompt",
L"Testing Shell prompt...",
IDS_STRING_1001,
IDS_STRING_1001,
IDS_STRING_1001,
wButtons,
ST_CENTERTITLE | ST_UNDERLINE,
AEE_FONT_BOLD,
AEE_FONT_BOLD,
100};//changed this to 0 as well
ISHELL_Prompt(pMe->piShell, &pi);

I tried on that simulator as well but didn't see any issues. Here is what I did:
uint16 wButtons[2] = {IDS_STRING_1001, IDS_STRING_1001};
AEEPromptInfo pi = { STATICWGTAPP_RES_FILE,
L"Test prompt",
L"Testing Shell prompt...",
IDS_STRING_1001,
IDS_STRING_1001,
IDS_STRING_1001,
wButtons,
ST_CENTERTITLE | ST_UNDERLINE,
AEE_FONT_BOLD,
AEE_FONT_BOLD,
100};//changed this to 0 as well
ISHELL_Prompt(pMe->piShell, &pi);