Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi, If you are using the AppWizard which is provided by Renesas you can select a BSP for the RX65N from within the AppWizard. Go to Project -> Edit Options In the upcoming dialog you can select a BSP for the RX65N Envision Kit. The BSP will be located in the AppWizard project directory in the "Target" folder: c:\AppWizard\<ProjectName>\Target\ This can be opened with e²Studio. Regards, Sven

  • Hi, If you are referring to a WINDOW (ID_WINDOW_00) added with the AppWizard you could do the following: C Source Code (35 lines)Now the DROPDOWN is a child widget of the window (ID_WINDOW_00) and the DROPDOWN notifications are getting send to _cbWin. If you mean a "normal" WM-window you might want to refer to this example. Quote from alpe: “but other interaction overlap other windows and should hide the dropdown ” Not sure what you mean with that. Regards, Sven

  • Hi, The handle "pMsg->hWin" refers to is always the handle of the window where the callback function belongs to. In the AppWizard output files (e.g. ID_SCREEN_00_Slots.c) you will find the callback function as shown below. Here the handle "pMsg->hWin" refers to the screen with the Id ID_SCREEN_00 (most likely the main screen). C Source Code (3 lines) So, if you like add a normal emWin widget to this screen you could something like: C Source Code (8 lines) Now, the dropdown widget is a child wind…

  • Hi, Yes, you can do that. Maybe like this: C Source Code (5 lines)But without a loop you can not do things like animations ore create timer with emWin. Also, do not call GUI_Exec() from a callback function of a window. BTW, the following three calls shouldn't be required: C Source Code (3 lines) Multibuffering is not available when using the GUIDRV_FlexColor driver. The layer specific calls are not required if using only one layer. Anyway, since you have only one layer you had to call these func…

  • Hi, you can simply create another window over the existing one to draw over the rest. Try this: C Source Code (93 lines)Please note that any underlaying windows/widget will no longer receive touch input with the window in the foreground. Regards, Sven

  • Hi Tanaka, The reason for the slow drawing performance might be the following. Strings are getting drawn as bitmaps. These are getting drawing most likely line wise causing quite some traffic on the bus. Depending on the drawing mode emWin also has to read back pixel data from the display causing even more traffic. To reduce the traffic you can use a buffer, either a cache or a memory device. Instead of writing line wise to the display emWin will complete the drawing operation in the buffer and,…

  • Hi, yes, this is a known issue and is already addressed. The reason is the clipping rectangle clipping the drawing into the memory device. With the latest emWin version we have introduced a function to get around this. You might try to temporarily increase the window size to the size of the memory device before drawing into the device. After filling the device restore the window to its intended size. Try this before writing to the memory device: C Source Code (24 lines) Depending on the library …

  • Hi, Something like this (attached)? I create one window with a button. On button release I create a second window and delete the first. The second window has also a button. On press I create the first one again and delete the second one. Regards, Sven

  • Hi, Every time GUI_Exec1() has done something it returns 1. If there is nothing left to do it returns with 0 but has done something. Therefore a second call of APPW_Exec() is required. Quote from TechGUI: “When will such situation occur? ” As long as there is something to do you will stay in the loop. This can be keeping the touch screen pressed or constantly redrawing something. Regards, Sven

  • Hi, It seems that the GUIDRV_FlexColor driver is already compatible to this controller. We have two GUIDRV_FlexColor variants which are mostlikely compatible. These variant are GUIDRV_FLEXCOLOR_F66720 and GUIDRV_FLEXCOLOR_F66709. I would try the GUIDRV_FLEXCOLOR_F66709 first, this one supports already a lot of controllers. The only thing I'm wondering about is that the data sheet of the GC9A01A does not say anything about reading the display data RAM (DDRAM). If it is not possible to read out th…

  • Hi, you can set your own copy-buffer-function. In this function you simply do nothing. C Source Code (7 lines) You can call the LCD_SetDevFunc() at the end of LCD_X_Config(). Regards, Sven

  • Hi, The AppWizard automatically tries to enable multibuffering although it is not available. This causes automatic cache operations being disabled and the cache on driver side has no effect. We will double check this and change the behavior if necessary. Try to deactivate multibuffering by calling WM_MULTIBUF_Enable(0); after calling APPW_Init(). Regards, Sven

  • Hi, Quote from Andy_AN2: “1) _acExplosion_200x150 This video is making the problems. In his callback it does: case GUI_MOVIE_NOTIFICATION_PREDRAW: GUI_MULTIBUF_Begin(); break; case GUI_MOVIE_NOTIFICATION_POSTDRAW: GUI_MULTIBUF_End(); break; ” As you already discovered, simply replace the multibuffering calls by the LCDControlCache() stuff. Quote from Andy_AN2: “However in MOVIE_ShowFeatures.c there is no WM_MULTIBUF_Enable() instruction. So maybe these GUI_MULTIBUF_Begin/_End(); are some remaini…

  • Hi, The GUI_SetRefreshHook() function is what I wanted to suggest. Try something like this: C Source Code (16 lines) The driver needs to use a cache. When using the Window Manager you have to do nothing else, it will take care of locking/unlocking the cache. If not using the Window Manager you can use LCD_ControlCache(LCD_CC_LOCK) and LCD_ControlCache(LCD_CC_UNLOCK) before and after a drawing operation. Do NOT use WM_MULTIBUF_Enable() in your application. This would disable the locking mechanism…

  • Simultaneous motion

    SEGGER - Schoenen - - emWin related

    Post

    Hi, please try to use the animation module of emWin instead of the motion support. Regards, Sven

  • Hi, please try to "unoptimize" the GIF as described under link below: segger.com/doc/UM03001_emWin.html#IMAGE_SetGIF Regards, Sven

  • Hi, The test screen looks almost good. See attached on how it should look like. After drawing the red, green and blue rectangles and the strings a large rectangle gets drawn with invert mode. If this is not being displayed properly it is most likely that the read function is not working right. If it is not possible to read from the display (for what reason ever) it is mandatory to use display cache. To invert the colors emWin needs to read the pxel data and write it inverted back to the LCD. Wit…

  • Hi, Please try the code below. It draws a test pattern on the display. C Source Code (25 lines) Can you send me a photo of the output? Best regards, Sven

  • Hi, Are you referring to the size of the generated c-file or the xbf-file? The size of the c-file doesn't say anything about the size on the target. I just gave it a try and the generated xbf-file has a size of ~20KB with the following code point ranges: 0x0000 - 0x007F 0x0100 - 0x017F 0x0180 - 0x024F The size of the font is 24 pixel. Of course, it depends pretty much on the font itself how much data are included in the file. The size of the xbf-file is the size it takes on the hardware. Which f…

  • Hi, Regarding multiple character drawing, can you send me your LCDConf.c (I guess NXP names it emwin_support.c). So, I can take a look into it. Not sure what might cause this behavior, yet. Quote from Suresh: “Is this enough to run Appwizard Application? ” 16K is not that much memory... Typically we recommend to have at least 130K available. Regards, Sven