Search Results

Hi Adrian, I'm sorry but I have seen your answer just now. Anyway thank you for support. I will keep you informed. Best regards, Valter Rasicci

Hello Adrian, I confirm that we are using emWin 5.24h in binary format. In fact I activated NXP to find a solution on this. However, deleting a task (and consequently exiting from any routine running in it) is a normally used method (implemented in several circumstancies like in lwIP for example) but, obviously, memory consistency must be kept when task is deleted; and using binary emWin routine this cannot be done. My problem is that,at the moment, I have no way to exit from GUI_JPEG_DrawScaled…

Hi Adrian, looking at the issue we shown, I have another important consideration. I tried to call GUI_JPEG_DrawScaledEx() routine in a separate task (we use freeRTOS) so that I delete this task when I need to exit before routine is completed; it seemed to work but soon emwin crashes. I suppose that emWin manager will allocate memory when I call GUI_JPEG_DrawScaledEx() to do the operation but, when I delete the task, that memory is cannot be deallocated! Sooner or later memory will terminate and …

Hi Adrian, thank you for your reply. Are you able to forecast when this update will be available? I think this could be a serious limitation because, when you call GUI_JPEG_ScaledEx() routine, you have no way to exit from it and, if you started a huge JPEG file procedure, you have to wait unacceptable time to recover from that situation. For example, try to imagine a photoframe and you want exit quickly from it ..... Best regards, Valter Rasicci

Dear sirs, we are using binary format emWin 5.24 version with LPC1788 processor. We use GUI_JPEG_DrawScaledEx(GUI_GET_DATA_FUNC * pfGetData, void * p, int x0, int y0, int Num, int Denom) and we need to exit from this routine before it is normally completed. Looking at emWina manual (page 174, paragraph 8.5 Getting data with the ...Ex() functions), they write: Return value The number of bytes which were actually read. If the number of read bytes does not match, the drawing function will return im…

Hi Adrian, it works on a PC. The problem is that it causes crash on the whole application when running on LPC1788 mpu. Moreover we used GUI_JPEG_DrawScaledEx instead of your GUI_JPEG_Draw. Really, just yesterday, we read in the following link http://www.keil.com/pack/doc/mw/graphic/html/release.html , in Program corrections section that some problems where effectively present on the library and it was solved on 5.24a version. Please look at the section we coloured in red we reported below. Moreo…

Dear sirs, by long time we are successfully using emWin. We use emWin on NXP LPC1788 mcu + 4.3 or 7 inches color displays. During the last days we are facing a very strange problem on JPG file visualization. We normally use GUI_JPEG_DrawScaledEx(GUI_GET_DATA_FUNC * pfGetData, void * p, int x0, int y0, int Num, int Denom) but some JPG file make the whole application crash!! The file is normally shown on PC/Windows and it is not a dimension/memory problem; it seems it is related to that file only!…

Hello Adrian, what you suggest is effectively what I did!! Instead GUI_MEMDEV_Delete(xxx) I created my own one: Valter_MemdevDelete(xxx) where, inside, I operate as you suggest. Best regards, Valter

Hi Adrian, ok I'll try to explain better. This post is related to my previous one (you answered today) Strange behaviour on GUI_MEMDEV_Delete() function created last 8 january by me. Normally I create memory devices as follow: md = GUI_MEMDEV_CreateFixed(X,Y,SIZEX,SIZEY,GUI_MEMDEV_NOTRANS,GUI_MEMDEV_APILIST_32,GUI_COLOR_CONV_888 ); - if md creation is successfull, md is assigned with an integer value !=0; - if md creation fails, md=0 is assigned; now here are 3 situations I described: A) just a…

Dear sirs, proceeding with problems in GUI_MEMDEV_Delete(md) function, I found the following: - if you call GUI_MEMDEV_Delete(md) and md=0, it works (I saw debugging in assembly that if parameter passed is 0, it returns immediately); - if you call GUI_MEMDEV_Delete(md) and md!=0, it works ONLY IF md was created (so md!=0) and is still "alive"; - if you call GUI_MEMDEV_Delete(md) and md!=0 but md was previously already deleted, it crashes. Now, it is clear that there is no reasons to delete an al…

Hi Adrian, Any news? Valter

Hi Adrian, sorry for my message that was not properly formatted. Please look at attached file containing considerations and source code. Best regards, Valter Rasicci

Just for confirmation, look at this source code lines: GUI_MEMDEV_Handle md[5]; /*THIS for CYCLE WORKS PERFECTLY (even though it is formally erroneous)!!*/ for(i=0;i<5;i++) WM_DeleteWindow(md); /*THIS for CYCLE CAUSES microprocessor HardFault() (even though it is formally correct)!!*/ for(i=0;i<5;i++) GUI_MEMDEV_Delete(md[i]); Best regards, Valter Rasicci

Hi all, I'm using emWin 5.18 on NXP LPC1788 device with gcc compiler. Sometimes I see that calling GUI_MEMDEV_Delete(memdev) causes HardFault_Handler(), that is microprocessor crash ..... It does not matter whether memdev was created or not before GUI_MEMDEV_Delete(memdev) call. It is not a problem due to memory overflow because often it happens when I call routine the first time. memdev is created with GUI_MEMDEV_CreateFixed() and normally it works properly. Just to try, I saw that it seems to …

Ok, Adrian. Thanks a lot, Valter Rasicci

Hi Adrian, thanks a lot ... I solved in another way using WINDOW instead of BUTTON .. the question was not solved simply using WM_CF_HASTRANS flag. But I saw that the WM_GetId(Fin1) function doesn't work on WINDOW widgets; it returns always 0. Do you confirm this? I tested on Simulator software and on device also. If I create 2 widgets as follow: But1 = BUTTON_CreateEx(100,220,220,50,WM_HBKWIN,WM_CF_SHOW,0,GUI_ID_BUTTON0); Fin1 = WINDOW_CreateEx(100,20,220,50,WM_HBKWIN,WM_CF_SHOW,0,GUI_ID_CHECK2…

Dear sirs, we want to obtain buttons with a trasparency level in unpressed state and another transparecy level when pressed. So the button has to show, with indicated level of transparecy, what is drawn "under" him. We made lots of test using all examples in emWin Simulator without result. Please find below my brief explanation: 1) when button is created everything is OK: unpressed state is properly shown; 2) button color in unpressed state is defined as GUI_BLACK | 0x80000000, and it is ok (onl…