Search Results

Quote from SEGGER - Adrian: “Defining dialog behavior” Sorry, Can not understand you. The example in user manual execute same function for button message(in WM_NOTIFY_PARENT) and dialog message. When "Enter" key is pushed, the message should be sent to button. However, the message was sent to dialog. So, the action was the function inside case WM_KEY, but not inside WM_NOTIFY_PARENT.

Quote from SEGGER - Adrian: “Hello, Could you please tell me which widget you use? Do you use Skinning? Thank you. Best regards, Adrian” I mean the widgets which are focus-sable as button, slider,edit.... The default focus frame is dash line with 1 pixel. I want a thicker line.

There is a roughly solution. API: EDIT_SetFocussable(); BUTTON_SetFocussable() Some widgets don't have this API.

Quote from achieveforce: “Hi, I am testing a small example program that has a dialog, within which a message box with an OK button is shown by the callback function of the dialog. I noticed that after pressing the Enter key to dismiss the message box, the Enter key is always passed to the parent (the dialog). So, my understanding is that, if a dialog has a widget with the focus (like a message box as above mentioned), the key press to the widget is supposed to be consumed by the widget and NOT b…

The default focus frame is made of dash line. It's very thin (1 pixel for width), and looks not clear. How can we make the line thicker for all widget with focus-able?

Quote from SEGGER - Adrian: “Hello Dario, Skinning properties can be changed for every type of widget. So if your widgets are of the same type, the skinning properties will apply to both of them. For details, please refer to the chapter "Skinning" in the emWin user manual. Best regards, Adrian” Hi Adrian, sorry, I don't agree with you. I see an API <WIDGET>_SetSkin(hFrame, My_DrawSkinFlex_FRAME) which is able to set skin for each widget. How do you think?