Using memory devices with transparency

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

  • Using memory devices with transparency

    Hello to everyone,

    I'm working with emWin simulator and trying to implement a simple speedo- (or any other-) meter, just an abstract scale on the background and a needle moving under that scale.
    My idea is to use GUIBuilder for creating a window, placing a scale image and placing a needle image vertically upwards using IMAGE widget.
    After that I create a memory device as a source device for vertical needle and draw the needle image into this device from array (dta) generated by GUIBuilder.
    Next I create a second memory device as a destination for turned needle and set background colors as transparent in both devices.
    Next I create a PROGBAR widget under the scale with the same size as a second destination memory device. This PROGBAR is needed just for setting a value and triggering its WM_PAINT message and rotating the needle within the borders of this PROGBAR according to its value using memory devices instead of showing a real PROGBAR.

    My problems are:
    - memory devices have no transparency (the dest device with the black background);
    - artifacts (old needle position) when rotating the needle.

    Can anyone help with my problem.

    Thanks for your time.

    LCD size in simulation is 1024x768.
    NUM_BUFFERS is 3.

    My simple code:
    Main.c:

    C Source Code: Main.c

    1. #include "GUI.h"
    2. #include "DIALOG.h"
    3. #include "IMAGE_Private.h"
    5. #define RECOMMENDED_MEMORY (1024L * 5)
    7. WM_HWIN CreateWindowMeter(void);
    9. void MainTask(void) {
    10. GUI_Init();
    12. WM_MULTIBUF_Enable(1);
    14. //
    15. // Check if recommended memory for the sample is available
    16. //
    17. if (GUI_ALLOC_GetNumFreeBytes() < RECOMMENDED_MEMORY) {
    18. GUI_ErrorOut("Not enough memory available.");
    19. return;
    20. }
    21. CreateWindowMeter();
    23. while(1)
    24. {
    25. GUI_Delay(50);
    26. }
    27. }
    Display All


    Some code in WindowMeterDLG.c (attached):

    C Source Code: WindowMeterDLG.c

    1. ...
    2. GUI_MEMDEV_Handle hMemArrowSrc, hMemArrowDst;
    3. PROGBAR_Handle hProgbar;
    4. GUI_RECT pRect1, pRect2;
    5. int Val, dVal;
    6. WM_HTIMER hTimer;
    7. ...
    9. static void _cbProgbar(WM_MESSAGE * pMsg) {
    10. GUI_RECT pRect;
    11. int Val;
    13. switch (pMsg->MsgId) {
    14. case WM_PAINT:
    15. // get the relative coordinates of the PROGBAR area
    16. WM_GetClientRect(&pRect);
    17. // get the PROGBAR value
    18. Val = PROGBAR_GetValue(pMsg->hWin);
    19. // select the dest device
    20. GUI_MEMDEV_Select(hMemArrowDst);
    22. // clear it with transparency
    23. GUI_SetBkColor(GUI_TRANSPARENT);
    24. GUI_Clear();
    26. // rotate the source device and save the result in dest device
    27. GUI_MEMDEV_Rotate(hMemArrowSrc, hMemArrowDst, pRect1.y1 + 1 - pRect1.x1 - 1, 0, (90 - Val * 180 / 100) * 1000, 1000);
    28. // select lcd
    29. GUI_MEMDEV_Select(0);
    31. // get the absolute coordinates of the PROGBAR area
    32. WM_GetWindowRect(&pRect);
    34. // show the rotated needle
    35. GUI_MEMDEV_WriteAt(hMemArrowDst, pRect.x0, pRect.y0);
    36. break;
    37. default:
    38. PROGBAR_Callback(pMsg);
    39. break;
    40. }
    41. }
    43. static void _cbDialog(WM_MESSAGE * pMsg) {
    44. const void * pData;
    45. WM_HWIN hItem;
    46. U32 FileSize;
    47. // USER START (Optionally insert additional variables)
    48. int val;
    49. // USER END
    51. switch (pMsg->MsgId) {
    52. case WM_INIT_DIALOG:
    53. //
    54. // Initialization of 'WindowMeter'
    55. //
    56. hItem = pMsg->hWin;
    57. WINDOW_SetBkColor(hItem, GUI_MAKE_COLOR(0x00472D16));
    58. //
    59. // Initialization of 'ImageMeterBckgnd'
    60. //
    61. hItem = WM_GetDialogItem(pMsg->hWin, ID_IMAGE_0);
    62. pData = _GetImageById(ID_IMAGE_0_IMAGE_0, &FileSize);
    63. IMAGE_SetDTA(hItem, pData, FileSize);
    64. //
    65. // Initialization of 'Image'
    66. //
    67. hItem = WM_GetDialogItem(pMsg->hWin, ID_IMAGE_1);
    68. pData = _GetImageById(ID_IMAGE_1_IMAGE_0, &FileSize);
    69. IMAGE_SetDTA(hItem, pData, FileSize);
    70. // USER START (Optionally insert additional code for further widget initialization)
    71. hItem = WM_GetDialogItem(pMsg->hWin, ID_IMAGE_1); // get the needle image widget handlder
    72. WM_HideWin(hItem); // hide it, don't need anymore
    74. WM_GetClientRectEx(hItem, &pRect1); // get the relative coordinates
    75. WM_GetWindowRectEx(hItem, &pRect2); // and the absolute coordinates of the image for memory devices
    77. // create a source and dest devices
    78. hMemArrowSrc = GUI_MEMDEV_Create(0, 0, pRect1.x1 + 1, pRect1.y1 * 2 - pRect1.x1 + 1);
    79. hMemArrowDst = GUI_MEMDEV_Create(0, 0, GUI_MEMDEV_GetYSize(hMemArrowSrc), GUI_MEMDEV_GetYSize(hMemArrowSrc) / 2 + (pRect1.x1 + 1) / 2);
    81. // copy the vertical needle image to the source device
    82. GUI_MEMDEV_Select(hMemArrowSrc);
    83. GUI_SetBkColor(GUI_TRANSPARENT); // make it transparent
    84. GUI_Clear();
    85. GUI_DrawStreamedBitmapAuto(_acImage_1, 0, 0); // copy the image
    86. GUI_MEMDEV_Select(0); // select lcd
    88. // create a progbar under the scale with the size of dest device
    89. hProgbar = PROGBAR_Create(pRect2.x0 - WM_GetWinSizeY(hItem) + WM_GetWinSizeX(hItem), pRect2.y0, GUI_MEMDEV_GetYSize(hMemArrowSrc), GUI_MEMDEV_GetYSize(hMemArrowSrc), WM_CF_SHOW);
    90. WM_AttachWindow(hProgbar, pMsg->hWin); // attach to the current window
    91. WM_SetHasTrans(hProgbar); // hide it
    92. WM_SetCallback(hProgbar, _cbProgbar); // for handling WM_PAINT message
    94. dVal = 1; // for incrementing / decrementing the PROGBAR value
    96. hTimer = WM_CreateTimer(pMsg->hWin, 0, 50, 0); // for changing the PROGBAR value every 50 ms
    97. // USER END
    98. break;
    99. // USER START (Optionally insert additional message handling)
    100. case WM_TIMER:
    102. Val += dVal; // incrementing / decrementing the PROGBAR value
    103. if ((Val > 100) || (Val < 0))
    104. dVal = -dVal; // change the sign for incrementing / decrementing
    106. PROGBAR_SetValue(hProgbar, Val); // set the PROGBAR value
    108. WM_RestartTimer(hTimer, 50); // restart the timer
    109. break;
    110. // USER END
    111. default:
    112. WM_DefaultProc(pMsg);
    113. break;
    114. }
    115. }
    Display All
    Files

    The post was edited 10 times, last by LexaGB ().

  • Hi,

    Which color conversion are you using?
    Did you saved the arrow image in the proper format?
    Which version of emWin is it?
    Can you attach your configuration files (GUIConf.h and LCDConf.c)?

    It seems that somehting doesn't fit.

    Regards,
    Sven
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello,

    I'm using Visual Studio 2010.
    I rebuilded the solution using "emWin Simulation & Trial version" pack downloaded from Segger's site (all header files, lib files and other...).
    The emWin version noticed there is v5.46.
    The color conversion macro defined there is GUICC_888. Previously I used GUICC_8888.
    GUI_NUMBYTES is 0x280000 by default.
    The only change I made in LCDConf.c file is resolution (1024 x 768).
    I use Bitmap Converter v5.32 for converting the arrow image from STemWin pack by ST (not demo version from Segger).
    And also for generating dialog code I use GUIBuilder v5.32 from that pack.
    The arrow image is converted to pallete with minimum colors (3 colors for the arrow itself, and white color on the background is a transparency color (0xFFFFFF)).
    And then the arrow image saved as dta with RLE4 compression and assigned to the IMAGE widget in GUIBuilder.
    I attached config files, and also arrow image files (bmp and dta), and also main() code and dialog code once again.

    There are fewer artifacts but they still exist and also no transparency.

    Thanks for your time.

    Files

    • Files.7z

      (11.02 kB, downloaded 589 times, last: )

    The post was edited 9 times, last by LexaGB ().

  • Hello, Sven.

    I slightly changed the dialog code, memory devices are both 32 bpp now, color conversion is GUICC_8888.
    I checked the data in both memory devices using GUI_MEMDEV_GetDataPtr() function.
    As I see in the debug session the source mem device correctly filled with GUI_TRANSPARENT color. The data is: 0xFF000000, 0xFF000000...


    But the dest mem device contains no transparency neither after using GUI_Clear() with GUI_TRANSPARENT color nor after using GUI_MEMDEV_Rotate(). The data is: 0x00000000, 0x00000000...

    So I tried to fill the dest device with transparency manually with direct access to memory.

    C Source Code: WindowMeterDLG.c

    1. ...
    2. unsigned long * pix;
    3. ...
    4. pData = GUI_MEMDEV_GetDataPtr(hMemArrowDst);
    6. // clear it with transparency
    7. for (pix = (unsigned long *) pData; pix < (unsigned long *) pData + memdev_dst_size; pix++)
    8. *pix = GUI_TRANSPARENT;

    After that I see transparency on the screen but there are still artifacts.


    I attached full dialog source code. The other change is only GUICC_8888 in LCDConf.c.

    Thanks for your time.
    Files

  • Hi,

    I got it, this was a bit tricky. The problem is the PROGBAR widget. When it gets a new value set (in WM_TIMER) it will also get redrawn, but only a small rectangle of the PROGBAR. This causes not the complete area to be redrawn and results in such a strange behavior.

    The solution is to simply call WM_InvalidateWindow(hProgbar) right after setting a new value for it.

    Sometimes it can be much easier to set up a normal WM window and modify it to your needs. With widgets it can get tricky sometimes because you don't know how they do things (like in this case).

    Regards,
    Sven
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello, Sven

    It works!
    And I took your advice and changed the PROGBAR to a window using WM_CreateWindowAsChild() and just calling WM_Invalidate() for that window. In combination with manual filling the dest device with transparency it works fine.


    Thank you for your time.

  • Hi,

    It shouldn't be necessary to manually fill the device with transparnecy. It should work with GUI_SetBkColor(GUI_TRANSPARENT) and GUI_Clear().

    Regards,
    Sven
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.