Multiple queries regarding BUTTON

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

  • Multiple queries regarding BUTTON

    Hello all,

    I am a newbie in emWin library. I have installed Visual Studio 2015 and with the help of GUIBuilder tool, created a simple dialog with a button.
    I am trying to experiment actions on various button states like enabled, disabled, mouse hover, mouse clicked.
    For enabled and button clicked, I successfully tried using BUTTON_SKINPROPS_PRESSED.

    But for disabled and mouse hover, I haven't succeeded yet.
    Tried multiple options - BUTTON_SetFocussable(hButton, 0); or BUTTON_SKINFLEX_PI_DISABLED option.

    Could anyone please help me with a sample code snippet on how to set a button in disabled state and how to implement mouse hover action on a button?
    Looking forward to your valuable response


    Thanking you in advance,

    Lullaby

  • Hi Lullaby,

    Try the following code. There I set a diffrent skin if the mouse hovers over the button. The general style of the button keeps the same, only the colors are changing. For a disable button just uncomment the code at the end of the MainTask().

    C Source Code

    1. #include "DIALOG.h"
    3. /*********************************************************************
    4. *
    5. * Local code
    6. *
    7. **********************************************************************
    8. */
    9. /*********************************************************************
    10. *
    11. * _cbButton
    12. */
    13. static void _cbButton(WM_MESSAGE * pMsg) {
    14. BUTTON_SKINFLEX_PROPS Props;
    15. static BUTTON_SKINFLEX_PROPS DefaultProps;
    16. static int Once;
    17. GUI_RECT Rect;
    18. static int MouseOver;
    20. if (Once == 0) {
    21. //
    22. // Get the default button properties, but only once
    23. //
    24. BUTTON_GetSkinFlexProps(&DefaultProps, BUTTON_SKINFLEX_PI_ENABLED);
    25. Once = 1;
    26. }
    27. switch(pMsg->MsgId) {
    28. case WM_PAINT:
    29. //
    30. // Handle the drawing by the default callback of the button
    31. //
    32. BUTTON_Callback(pMsg);
    33. //
    34. // Get the area of the button to display some text centered in it
    35. //
    36. WM_GetClientRect(&Rect);
    37. GUI_SetTextMode(GUI_TM_TRANS);
    38. GUI_SetColor(GUI_BLACK);
    39. //
    40. // Check if mouse is inside button area or not, display proper text
    41. //
    42. if (MouseOver) {
    43. GUI_DispStringInRect("Mouse over button", &Rect, GUI_TA_HCENTER | GUI_TA_VCENTER);
    44. } else {
    45. GUI_DispStringInRect("Mouse not over button", &Rect, GUI_TA_HCENTER | GUI_TA_VCENTER);
    46. }
    47. break;
    48. case WM_MOUSEOVER:
    49. //
    50. // Configure the properties and set them, but only on the first time the mouse gets inside the button area
    51. //
    52. if (MouseOver == 0) {
    53. Props = DefaultProps;
    54. Props.aColorFrame[0] = GUI_DARKRED;
    55. Props.aColorFrame[1] = GUI_RED;
    56. BUTTON_SetSkinFlexProps(&Props, BUTTON_SKINFLEX_PI_ENABLED);
    57. BUTTON_SetSkinFlexProps(&Props, BUTTON_SKINFLEX_PI_FOCUSSED);
    58. //
    59. // Tell the button something has changed and trigger a redraw
    60. //
    61. WM_Invalidate(pMsg->hWin);
    62. }
    63. //
    64. // Set the mouseover flag
    65. //
    66. MouseOver = 1;
    67. break;
    68. case WM_MOUSEOVER_END:
    69. //
    70. // Set back to default properties
    71. //
    72. if (MouseOver == 1) {
    73. BUTTON_SetSkinFlexProps(&DefaultProps, BUTTON_SKINFLEX_PI_ENABLED);
    74. BUTTON_SetSkinFlexProps(&DefaultProps, BUTTON_SKINFLEX_PI_FOCUSSED);
    75. //
    76. // Tell the button something has changed and trigger a redraw
    77. //
    78. WM_Invalidate(pMsg->hWin);
    79. }
    80. //
    81. // Set the mouseover flag
    82. //
    83. MouseOver = 0;
    84. break;
    85. default:
    86. //
    87. // Any messages not handled by this callback are getting passed to the default callback of the button
    88. //
    89. BUTTON_Callback(pMsg);
    90. break;
    91. }
    92. }
    94. /*********************************************************************
    95. *
    96. * Public code
    97. *
    98. **********************************************************************
    99. */
    100. /*********************************************************************
    101. *
    102. * MainTask
    103. */
    104. void MainTask(void) {
    105. WM_HWIN hButton;
    106. BUTTON_SKINFLEX_PROPS Props;
    108. #if WIN32
    109. WM_SetCreateFlags(WM_CF_MEMDEV); // Automatic use of memory devices only in simulation, on hardware multibuffering should be used
    110. #endif
    111. //
    112. // Initialize GUI
    113. //
    114. GUI_Init();
    115. //
    116. // Set a BK color for the desktop window
    117. //
    118. WM_SetBkWindowColor(GUI_BLACK);
    119. //
    120. // Create a button and set a callback
    121. //
    122. hButton = BUTTON_CreateAsChild(10, 10, 150, 150, WM_HBKWIN, 0, WM_CF_SHOW);
    123. WM_SetCallback(hButton, _cbButton);
    124. //
    125. // Uncomment the code below to see what is happening for a disabled button
    126. //
    127. /*
    128. //
    129. // Fill Props structure
    130. //
    131. BUTTON_GetSkinFlexProps(&Props, BUTTON_SKINFLEX_PI_DISABLED);
    132. //
    133. // Re-set some values
    134. //
    135. Props.aColorFrame[0] = GUI_DARKGREEN;
    136. Props.aColorFrame[1] = GUI_GREEN;
    137. //
    138. // Set properties again and disable button
    139. //
    140. BUTTON_SetSkinFlexProps(&Props, BUTTON_SKINFLEX_PI_DISABLED);
    141. WM_DisableWindow(hButton);
    142. */
    143. while (1) {
    144. GUI_Delay(100);
    145. }
    146. }
    Display All


    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.