Search Results

Hi, does the window with the button always get deleted? If not, emWin will allocate memory every time a new button is created and every time a string is added. Best regards, Florian

Hello, could you let me know what hardware you are using and send me your LCDConf.c? Thanks and best regards, Florian

Hello, the routines BUTTON_SetBkColor() and BUTTON_SetFocusColor() only work in conjunction with the classic skin. The classic skin can be enabled by calling BUTTON_SetSkinClassic(). To change the color properties of a button that uses the default skin, skinning props should be used. With skinning props, the user enters the desired properties of a widget (e.g. the focus and background color of a button) into a static array. These properties can then be applied with BUTTON_SetSkinFlexProps(). I'v…

Hi, to keep the graph data, the dialog that contains the graph handles should not be deleted. You could hide the graph dialog when switching to another window and show the graph dialog again when opening it. So instead of deleting the windows and creating them again, you could use the routines WM_HideWindow() and WM_ShowWindow(). Best regards, Florian

Hi, it is not possible to add custom fonts to the GUIBuilder. Custom fonts can be created using the FontConverter. I'd only recommend using the GUIBuilder as a starting point for creating a dialog, since the tool doesn't have many features. Best regards, Florian

Hi, to create a button with a custom image, you should set a custom callback to the button widget and display a bitmap. Attached is an example. Best regards, Florian

Hi, you have to use the GUI_MAKE_COLOR to make colors from hex values (like GUI_MAKE_COLOR(0x00FF0000)). The predefined color macros don't need the GUI_MAKE_COLOR macro, so just enter e.g. GUI_BLUE as parameter. Best regards, Florian

Hello, you have to enter valid GUI_COLORs. You can use the predefined colors (GUI_WHITE, GUI_GREEN, etc...) or make your own colors using the GUI_MAKE_COLOR() macro. The colors are entered into this macro in the format ABGR. The alpha value is stored in the highest 16 bits. 00 is opaque, FF is transparent. For example, opaque blue looks like this: GUI_MAKE_COLOR(0x00FF0000). I'd suggest you to also read the "Colors" chapter in the manual to learn more about emWin's color format. Best regards, Fl…

Hello, WM_MULTIBUF_Enable() also works with more than one layer. WM_MULTIBUF_EnableEx() has a different purpose. Usually when a routine is not documented, it is not intended or unsafe to use. I'm not sure why there is still flickering after you enabled multi-buffering, but the error probably lies in your LCDConf.c. There are ready-to-use configurations located in the shipment folder under \Sample\LCDConf\<Driver>\<Hardware>. The correct configuration file might fix your problem. Best regards, Fl…

Hi, GUIBuilder is a free tool that does not have a premium version. A similar, but much more powerful tool is the AppWizard, which now comes with every emWin PRO shipment. You can read more info about it here: segger.com/products/user-inter…tools-overview/#appwizard Best regards, Florian

Hello Jan, unfortunately this is not possible without changing the emWin code. The only way would be to set a global flag always when calling DROPDOWN_SetSel() and instantly clearing the flag when reaching the WM_NOTIFY_PARENT case. When the flag would be set, the WM_NOTIFY_PARENT would be ignored. Best regards, Florian

Hi, the only way to do this in emWin is by using the super and subscripts Unicode offers. To use Unicode with emWin, GUI_UC_SetEncodeUTF8() has to be called. The Unicode characters need to be UTF8 encoded in the string. For example, "subscript 2" (compart.com/en/unicode/U+2082) would be "\xE2\x82\x82" in a C string. Lastly, it is also important that the font you are using includes the Unicode characters you want to display. Best regards, Florian

Hi, the function GRAPH_SCALE_SetOff() should achieve what you want. It offsets the text on a scale in the negative or positive X- or Y- direction, whether the scale object is horizontal or vertical. Best regards, Florian

Hi, .zip should work for you. Best regards, Florian

Hi, when the value of the SCROLLBAR changed, the notification code of the WM_NOTIFY_PARENT will be WM_NOTIFICATION_VALUE_CHANGED instead of WM_NOTIFICATION_RELEASED. This is intentional, since its value is what the widget is used for most of the times. For your purpose, I would just react on the WM_NOTIFICATION_VALUE_CHANGED code. This would make the most sense for scrolling through a text file. When the value changed, you can update your window accordingly, using the new scroll position. Best r…

Hi, WM_NOTIFY_PARENT messages will always be sent to the widget's parent window. So if a button gets clicked, the WM_NOTIFY_PARENT message goes to the button's parent. You can then check the pMsg->Data.v value for the notification code. For example, if it is WM_NOTIFICATION_RELEASED, it means a click on that widget has been released. I've attached a simple example that demonstrates this, hopefully this will help you understand the mechanism better. Best regards, Florian

Hi, unfortunately there is no function to do this for all button widgets, you have to overwrite the callback for every widget and react on the WM_KEY message. Best regards, Florian

Hi, the command WIDGET_ITEM_DRAW_OVERLAY only gets sent to LISTWHEEL widgets. As stated in the manual, only the following commands get sent to an OwnerDraw routine of a SWIPELIST: • WIDGET_ITEM_DRAW_BACKGROUND • WIDGET_ITEM_DRAW_TEXT • WIDGET_ITEM_DRAW_BITMAP • WIDGET_ITEM_DRAW_SEP This is because the SWIPELIST widget does not have that specific overlay unlike the LISTWHEEL. If you want to draw something like an overlay, it makes more sense to use an overwritten callback to draw freely instead o…

Hi, I tried to reproduce the behavior you noticed, but the widget always sent a WM_NOTIFY_PARENT message when releasing the press, and also when releasing outside of the scrollbar window. Best regards, Florian

Hi Evgeni, there are many ways to realize such a GUI you are describing. You could e.g. use different bitmaps to display the LED status or draw the LEDs yourself. You'll find lots of routines in the "2-D Graphic Library" chapter in the emWin manual for drawing. To answer your second question: yes, the timers will still be active. Timers are paired to a window and stay active as long as that window doesn't get deleted (or the timer runs out, of course). (There are also timers that are independent…