LPC1787 emWin library support required

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC1787 emWin library support required

1,131 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by kevingodfrey on Sun Jun 17 22:50:20 MST 2012
[FONT=Calibri]I would like some help with emWIN and emBOS and the keyboardmanager please.[/FONT][FONT=Calibri] [/FONT]

[FONT=Calibri]I am using GUI_SendKeyMsg() from my keyboard task when ahardware key press is detected.[/FONT]

[FONT=Calibri]I have another task that I want to use to display a graphicfor which key was pressed. [/FONT]
[FONT=Calibri] [/FONT]

[FONT=Calibri]static void _Task_0(void) {[/FONT]

[FONT=Calibri]  WM_HWIN hWin;  [/FONT]

[FONT=Calibri]  hWin = GUI_ExecDialogBox(_aDialogCreate,GUI_COUNTOF(_aDialogCreate), &_cbCallbackT0, 0, 0, 0);[/FONT]

[FONT=Calibri]  [/FONT]

[FONT=Calibri]while(1)[/FONT]

[FONT=Calibri]  {[/FONT]

[FONT=Calibri]   WM_SetFocus(hWin);[/FONT]

[FONT=Calibri]    GUI_WaitKey();[/FONT]

[FONT=Calibri]    GUI_Delay(1000);[/FONT]

[FONT=Calibri]}[/FONT]

[FONT=Calibri]}[/FONT]

[FONT=Calibri] [/FONT]

[FONT=Calibri]Within the call-back for the above dialog box I have thefollowing check for the key. I have a breakpoint set here to capture the keyevent.[/FONT]

[FONT=Calibri] [/FONT]

[FONT=Calibri]case WM_KEY:[/FONT]

[FONT=Calibri]    switch (((WM_KEY_INFO*)(pMsg->Data.p))->Key)[/FONT]

[FONT=Calibri]    {[/FONT]

[FONT=Calibri]      case GUI_KEY_UP:[/FONT]

[FONT=Calibri]        hItem =WM_GetDialogItem(pMsg->hWin, ID_IMAGE_0);[/FONT]

[FONT=Calibri]       IMAGE_SetBitmap(hItem, &bmarrow_up);//GUI_EndDialog(hWin, 1);[/FONT]

[FONT=Calibri]        break;[/FONT]

[FONT=Calibri]      case GUI_KEY_ENTER:[/FONT]

[FONT=Calibri]       GUI_EndDialog(hWin, 0);[/FONT]

[FONT=Calibri]        break;[/FONT]

[FONT=Calibri]        };[/FONT]

[FONT=Calibri]      break;[/FONT]

[FONT=Calibri] [/FONT]

[FONT=Calibri] [/FONT]

[FONT=Calibri]My problem is that I don’t reach this breakpoint after thekey is pressed and GUI_SendKeyMsg() is called. [/FONT]

[FONT=Calibri]The way I understand this, the callback is called after theGUI_SendKeyMsg() is called, is this correct?[/FONT]
0 Kudos
Reply
5 Replies

1,045 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by SimonThome on Tue Jun 19 00:41:07 MST 2012
thanks, I will try there
0 Kudos
Reply

1,045 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Tue Jun 19 00:26:09 MST 2012
I'm not sure how many emWin users frequent the LPCXpresso forum. You might do better posting to NXP's graphics forum on lpcware.com for assistance on the NXP emWin variant...

http://www.lpcware.com/forums/peripherals-forums/graphics

Regards,
CodeRedSupport
0 Kudos
Reply

1,045 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by SimonThome on Mon Jun 18 07:17:17 MST 2012
The thing is I have emailed Segger emWIN support, and they have said that NXP must provide support for the NXP/emWIN library. Basically they won't provide support because I have not paid for it and NXP holds this particular license.
0 Kudos
Reply

1,045 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Mon Jun 18 07:13:31 MST 2012
You'll probably get better help on emWin on the emWin forum:
http://www.segger2.com/index.php?boardID=3&page=Board
0 Kudos
Reply

1,045 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by SimonThome on Mon Jun 18 04:21:17 MST 2012
Hi everyone,

kevingodfrey and I are working on this together.

I have figured out what the problem is... It's because I was using virtual key codes, in particular arrow keys. So it seems that the widgets handle these keys on their own with out the need for user code, and therefore do not post a WM_KEY event to the callback function.

I would like to know if there is a way of disabling this automatic handling of the keyboard, and handle all of the key presses in my own code within the callback functions?

thanks,
Simon
0 Kudos
Reply