Search Results

Hi, I've checked the BDF-font unifont-9.0.06.bdf. It does not contain the characters 0xFFFE and 0xDF7E. The problem with not finding existing codepoints immediately after reading a BDF file is now fixed. Thanks for the hint. Best regards, Jörg

Hi, I've checked that. It worked without any problem with the simulation project shipped with emWin. It also works with the evaluation version. Regards, Jörg

Hi Matz, I assume you are using the function GUI_LANG_GetTextEx() to access the text. Please note that ALL text returned by that function remains valid in any case. The function GUI_LANG_GetTextBufferedEx() does not allocate memory. Best regards, Jörg

Hi, sounds weird. A NULL pointer is returned if the memory device handle itself is 0. Too less memory configured? A memory device of 320x240 requires a memory block of '320 x 240 x BytesPerPixel'. Regards, Jörg

Hi, a) Yes, as explained in the documentation. Excerpt: "If a hardware supports multiple layers and the ability of layer positioning emWin can be configured to use a separate layer for managing the cursor." b) “GUI_AssignCursorLayer()” should be used. c) Should be explained in detail under “GUI_AssignCursorLayer() in chapter 'MultiLayer API' Regards, Jörg

Hi Marco, please note that a function/tool for replacing the content of a SVG-file by function calls of the emWin's '2-D Graphic Library' is not possible. Regards, Jörg

Hi, Your function is legit. WM_BroadcastMessage() sends its own copy of the given message. Regards, Jörg

Hi, Thank you very much for the hint. Will be considered in the future. Regards, Jörg

Hi, You could overwrite the callback function of the TEXT widget. For all events except WM_PAINT you should call the default text widget callback function TEXT_Callback(). Within the WM_PAINT event the default function should be called first and then other things could be drawn on top. The sample WIDGET_ButtonRound() shows how to overwrite a callback function. Regards, Jörg

Hi, You wrote: "Register 0xA0 bits 7:6 set the colour depth. 00b is 256 colour" Please note that this is not right: [img]data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKsAAABBCAIAAAAhVcOqAAATGUlEQVR4nO2caVAUx/vHf1XJy7zUqlSSMlKJVJBDwQMDMQRETgmKnCKHUQNiFOVQINwqN3LKLi4gu8upBbhsISIs96nAIgsCAsvucimwwHK57DHP/0VXpvYPajxIou5+q1/09HT39PR8Zqbn6afnf/BOunr16rsVVOhD0//erZiCgE9GCgLkXQoC5F0KAuRdCgLkXQoC5F0KAuRdCgLkXQoC5F0bQEBPT4/srlu3bpFIJA6HMzIyQv9L8/Pza2pgMplNTU18Pp9EIiUlJb30KDU1NRkZGd3d3RwO501a1dfXR6VSi4uLO…

Hi, please note that this is a hardware related problem without any impact to emWin. Based on our experience using a refresh rate different to the recommended refresh rate does not harm the LCD. If nothing flickers and all works as expected 38.5 MHz should be ok. Regards, Jörg

Hi, could you please check what exactly causes the bus fault? Regards, Jörg

Hi, Yes, that is normal. The prototype of the function is as follows: void WM_SendMessageNoPara(WM_HWIN hWin, int MsgId); It does not consider the sender. But you can use WM_SendMessage() and fill the message structure with the required information. Regards, Jörg

Hi, the animation functions based on memory devices require more RAM than 0x30000 bytes in your case. For fading in a window a memory device (32bpp) for the window to be faded in is required, a working device for the animation and a background device is required. Regards, Jörg

Hello, what exactly stucks when pressing 2 points the same time? I do not think that using Multi touch support solves the problem. For me it is not clear what exactly is the problem. If there is touch input it should be stored into the PID-buffer using GUI_PID_StoreState() or GUI_TOUCH_StoreState(). Could you please give us a better impression of what does not work as expected? Neglecting input outside of a window could be achieved with modal windows. Regards, Jörg

Hi, decompressing an image of 783*502 pixels needs app. 96KByte of RAM in case of a non progressive JPEG. I assume there is not enough memory available. May be the WM has taken the available memory for an automatic memory device. Suppressing use of a memory device for that window may helps. Regards, Jörg

Hi, what exactly is the problem with that version? The simulation works with all preceding versions. Regards, Jörg

Hi, The behavior of emWin in that case could not be changed. If a window is touched, all ancestors receive that message. A solution could be overwriting the callback function of the GRAPH widget. It receives that message at first before it is also send to the parent of the GRAPH. I hope that helps. Regards, Jörg

Hi, we recommend that drawing operations should be done only within the WM_PAINT event as explained in the documentation. If drawing is done outside a WM_SelectWindow() is required. Regards, Jörg

Hello, if GUI_MEMDEV_CreateFixed() returns with zero there is not enough memory available for the memory device. Please increase the size of the memory block assigned to emWin in GUI_X_Config(). Regards, Jörg