Search Results
Search results 1-20 of 39.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Dropdownbox error
PostHi Adrian, Some feedback for you. I am using 5.24h from NXP, and so far the dropdown widget is working nicely. The document needs a correction for the DROPDOWN_SetItemDisabled function: the OnOff parameter should be 1 = disable and 0 = enable. It is the other way around at the moment. Thanks.
-
Memory allocation
PostJust a thought... If one needed to update the language files in RAM at run time, for example in a situation where a new csv file is loaded into the file system by the user. Would I have to re initialize emWin to load the new CSV files? Or is there another way to re-load the updated CSV file into RAM using GUI_LANG_LoadCSV() This could also get tricky in a multitasking environment if the file were uploaded whilst the GUI tries to access a language string
-
Dropdownbox error
PostThanks Adrian! I will request this update from NXP
-
Memory allocation
PostThanks Adrian!
-
Memory allocation
PostNot sure how to attach files on this forum so I have emailed it to support @ segger.com, for your attention. Thanks.
-
Memory allocation
PostOk not too much of a problem for me to change, I can see now why it was done this way. Perhaps the documentation should be a little more clear on this, that only one CSV can be opened otherwise you run into memory problems. In the document is says: "This function call first deletes all existing text resources", so I assumed it was ok to call GUI_LANG_LoadCSVEx() multiple times as it would delete the previous resource (and associated allocated memory) By the way I have found execution speed much …
-
Memory allocation
PostHi Adrian, I want to make sure I understand this correctly, are you saying that GUI_LANG_LoadCSVEx() must not and cannot be called more than once during an application? That windows and dialogs may not have individual CSV language files, but rather the entire application must use a single CSV file for all text? Or Is this not a short coming with the way GUI_LANG_LoadCSVEx() allocates memory once it has been called? That is should be able to work multiple times across the application?
-
Memory allocation
PostThanks Adrian I am calling GUI_LANG_LoadCSVEx() before I create each dialog. (Each of my dialogs has its own language CSV file, which is called before calling GUI_CreateDialogBox(....) ) If I don't call this function at all, I no longer have the problem I mentioned above. Is there perhaps a problem with the memory allocation of the GUI_LANG_LoadCSVEx() function, or is there a way of flushing the langue buffer upon deleting a dialog?
-
Memory allocation
PostHi Adrian, I have noticed something strange with the memory allocation of emWin, please can you let me know if this is a problem or not. I am using the following code in my background GUI task to monitor the memory usage: static void GUIBackgroundTask(void) { WM_SetDesktopColor(GUI_BLACK); WM_SetCallback(WM_HBKWIN, _cbBackgroundWin); while(1) { GUI_Exec(); /* Do the background work ... Update windows etc. */ GUI_X_ExecIdle(); /* Nothing left to do for the moment ... Idle processing */ GUIFreeByt…
-
Dropdownbox error
PostHi Adrian, Do you have any feedback regarding this issue yet? Thanks.
-
Dropdownbox error
Posthere is an excerpt from my application: I have a dropdown with four arbitrary items in the list. The code below is called within a dialog callback function. When the second SetItemDisabled() is called below, I get this error: 0xEBB0 "GUI_Alloc.c:\nBlock to be deleted is already locked in _Free(..." I hope this is enough for you to debug. Thanks! { WM_HWIN hItem; hItem = WM_GetDialogItem(pMsg->hWin, ID_DROPDOWN_0); if(Settings) { DROPDOWN_SetSel(hItem, 4); //select the last item and disable the r…
-
Dropdownbox error
PostHi Adrain, I have sorted the spinbox problem out, I didn't reaise that the API had been updated, all I needed was to use the SPINBOX_SetEditMode() function, so please ignore the previous post. I am using 5.24D now and I still have a problem with the Dropdown box DROPDOWN_SetItemDisabled() function: When I call it more than once consecutively, I get the following error: "GUI_Alloc.c:\nBlock to be deleted is already locked in _Free(..." Please can you let me know if what the status is of this prob…
-
Dropdownbox error
PostHi Adrian, I have received V5.24B from NXP. And I have noticed that the cursor blinking on the spinbox widget is not working on this version. Is this also a known issue? When do you think NXP will have version D from Segger? It seems they only have version B at the moment.... Thanks
-
Dropdownbox error
PostThank you Adrian, I have asked NXP when they will be releasing this version on their forum, hopefully they don't take too long...
-
Dropdownbox error
PostHi Adrian, thanks for the quick feedback. Which version of emWin was this fixed in?
-
Dropdownbox error
Postwhen I use the DROPDOWN_SetItemDisabled() function it always produces the following GUI error: "GUI_Alloc.c:\nBlock is already unlocked in GUI_ALLOC_UnlockH(..." All the other Dropdownbox API functions are working correctly except this one. Is this a bug, or am I missing something? I can'f find any further information in the emWin documentation. Thanks in advance!
-
Hi Adrain, Please can you assist me with the FRAMEWIN_GetUserData & FRAMEWIN_SetUserData fucntions. I am using emWin in a full multitasking configuration i.e. Lowest priority task calls the emWin update functions, and another higher priority task manages the user interface. I have created a non-blocking dialog that contains a Framewin widget from within the user interface task (with extra user data defined for the Framewin widget in the resource table) I am calling FRAMEWIN_SetUserData from the …
-
I need to place my fonts in external memory as I am beginning to push the limits of my LPC1788 code space. Problem is that I am noticing that the performance of my application has become much slower since I have implemented XBF Fonts on my SD card (via emFile). I have tried assigning cache with the hopes of speeding the continual read process up, but it doesn't seem to make enough of a difference. Is there any other way of making this run faster? Maybe placing the entire font into external SDRAM…