Search Results

If I create an EDIT widget and set float mode using: EDIT_SetFloatMode(hObj, 0.0, -1000.0, 1000.0, 0, GUI_EDIT_SIGNED | GUI_EDIT_SUPPRESS_LEADING_ZEROES); Then the EDIT box is empty. This only occurs if the Value is zero, Shift is zero and both GUI_EDIT_SIGNED and GUI_EDIT_SUPPRESS_LEADING_ZEROES flags are set. If either flag is not set or the Shift parameter is greater than zero, then a value is seen in the EDIT box. Can this be fixed? Regards, Craig

The widgets that are hidden are not unwanted. Depending on user interaction I need to show/hide widgets on-the-fly. I could create and delete the widgets as needed, but the overhead and maintainability of the project would be negatively impacted. I have considered this as a work-around. I guess my question is why are hidden and disabled widgets able to receive focus? Is this really by design, or something that should be addressed with the library? Regards, Craig

Dear Ezio, Thanks for the reply. I am currently evaluating emWin for use in an embedded application that will use a number of keys (probably 9 in total). The aim is to provide dynamic information and configuration windows. The evaluation project creates a dialog window with a number of widgets for data entry. Depending on current configuration or options selected on the form, some widgets may be hidden. The widgets are navigated by the user using the keys. By injecting GUI_KEY_TAB/GUI_KEY_BACKTA…

Hello Adrian, Apologies, I should have been clearer. The example I gave in the original post of the DROPDOWN widget does have both WM_DisableWindow() and WM_HideWindow() called passing the widget handle. Still it is able to receive focus and keyboard events. Is there anyway to stop focus passing to such objects? Regards, Craig

I am creating dialogs with various widgets and injecting GUI_KEY_TAB/GUI_KEY_BACKTAB key presses to cycle focus through the widgets. If a dialog is created with hidden and/or disabled widgets, then these widgets can still accept focus, leading to some very strange behaviour. For example, try creating a DROPDOWN widget, call WM_HideWindow() on it and inject GUI_KEY_SPACE when it has focus. A disembodied LISTBOX appears where the hidden DROPDOWN would be displayed. How do I stop this unwanted beha…

When using EDIT_SetFloatMode(), you are required to set minimum and maximum values. If these are set to FLT_MAX * -1 and FLT_MAX respectfully, then the number is not displayed, and often a few random characters are seen. What is the maximum length of floating point numbers that can be displayed? Unfortunately I can not find any indication in the manual. Regards, Craig

When using EDIT_SetFloatMode(), you are required to set minimum and maximum values. If these are set to FLT_MAX * -1 and FLT_MAX respectfully, then the number is not displayed, and often a few random characters are seen. What is the maximum length of floating point numbers that can be displayed? Unfortunately I can not find any indication in the manual. Regards, Craig

Hello Adrian, Some further investigation shows that it is a problem with deleting menus that are currently not displayed. If I have a menu with four submenus (the submenus have item Ids of 100..103) then the following function call will delete the menu without faulting: void menuDestroy(MENU_Handle hMenu) { uint8_t i; MENU_Popup(hMenu, WM_HBKWIN, 0, 0, 0, 0, 0); for(i = 100; i < 104; i++) { MENU_ITEM_DATA item; MENU_GetItem(hMenu, i, &item); MENU_Popup(item.hSubmenu, WM_HBKWIN, 0, 0, 0, 0, 0); }…

Hello Adrian, I have checked (and double checked) the linker, etc. I have been very generous with stack sizes, memory pools and frame buffers. In total emWin has been allocated over 12MB of RAM. I have confirmed that task stacks and the emWin memory pool have not over run. Do you have any idea why I see the issue if the menu is created with a parent window of WM_UNATTACHED, but not if the parent window is WM_HBKWIN? Regards, Craig

Hello Adrian, Have you any thoughts on this problem? I am still struggling to see how to free the resources allocated to a pop-up menu. I have isolated the issue to just two lines of code. Simply creating the menu and deleting it straight away causes the bus fault when WM_DeleteWindow is called: MENU_Handle hMenu = MENU_CreateEx(0, 0, 0, 0, WM_UNATTACHED, 0, MENU_CF_VERTICAL, 0); WM_DeleteWindow(hMenu); However, if the menu is attached to a window: MENU_Handle hMenu = MENU_CreateEx(0, 0, 0, 0, W…

Hello Adrian, I do use two layers. Both are allocated memory and I can switch between them. Regards, Craig

Hello Adrian, I have adapted your exemplar code to test in my application: typedef struct { char * sText; U16 Id; U16 Flags; } MENU_ITEM; static MENU_ITEM _aMenuItems[] = { {"New game", 1, 0}, {"Pass", 2, 0}, {0, 0, MENU_IF_SEPARATOR}, {"Exit", 3, 0}, }; static void _AddMenuItem(MENU_Handle hMenu, MENU_Handle hSubmenu, const char* pText, U16 Id, U16 Flags) { MENU_ITEM_DATA Item; Item.pText = pText; Item.hSubmenu = hSubmenu; Item.Flags = Flags; Item.Id = Id; MENU_AddItem(hMenu, &Item); } static v…

Hello, I am developing an application which makes use of several pop up menus that are built on-the-fly. The menus are created using: MENU_Handle hMenu = MENU_CreateEx(0, 0, 0, 0, WM_UNATTACHED, 0, MENU_CF_VERTICAL, 0); and populated: static void prvAddEntry(MENU_Handle hMenu, const char *label, U16 id, U16 flags) { MENU_ITEM_DATA entry; entry.pText = label; entry.Id = id; entry.Flags = flags; entry.hSubmenu = 0; MENU_AddItem(hMenu, &entry); } If I need to display the menu, then calling: MENU_Po…