SEGGER - Florian Administrator

  • Member since Oct 24th 2019

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

  • SEGGER - Florian -

    Replied to the thread SWIPELIST, stop moving with zero overlap.

    Post
    Hello, Could you send me a sample to reproduce this behavior and also which emWin version you are using? Best regards, Florian
  • SEGGER - Florian -

    Replied to the thread Using Memory Device with Windows Manager.

    Post
    Hi, You can write the contents of a memory device into a window using GUI_MEMDEV_WriteAt(). You should make sure to delete the memory device when it is not needed anymore using the routine GUI_MEMDEV_Delete(). It makes sense to do this in a WM_DELETE…
  • SEGGER - Florian -

    Replied to the thread MULTIEDIT with widget on top.

    Post
    Hi, When a button is pressed or released, a WM_NOTIFY_PARENT message is sent to the parent of the button widget. So in this case, the MULTIEDIT would receive this message. You can also read about this in the user manual. To process the message, you…
  • SEGGER - Florian -

    Replied to the thread MULTIEDIT with widget on top.

    Post
    Hi, Is the button a child window of the MULTIEDIT? In my test moving the scrollbar of a MULTIEDIT did not affect the visibility of the button. C Source Code (8 lines) Can you send me a small example to reproduce this behavior? Thanks and best…
  • SEGGER - Florian -

    Replied to the thread Multiple displays with AppWizard on one target device.

    Post
    Hi WitDai, Currently multiple displays are not supported by AppWizard and we do not plan to add this feature in the near future. Right now setups with multiple displays are only supported by standard emWin. The user manual provides information about…
  • Hi, The routines LISTWHEEL_MoveToPos() and LISTWHEEL_SetPos() simply change the wheel position, but do not change the selection. LISTWHEEL_SetSel() should be used to set the selection. However, I just noticed that LISTWHEEL_SetSel() does not notify the…
  • SEGGER - Florian -

    Replied to the thread How to close a window when a button is pressed.

    Post
    Hi, Quote from giusloq: “Probably the sentence in the manual explains why GUI_ALLOC_GetNumFreeBytes() doesn't return the same number after one WM_CreateWindow() and one WM_DeleteWindow(). This is ok, but the number should be almost the same with the…
  • SEGGER - Florian -

    Replied to the thread How to close a window when a button is pressed.

    Post
    Hi, What you are describing is not a memory leak, but normal behavior of emWin's memory management. You can find a description about emWin's memory management in the manual under "Configuration -> Memory management". I have attached an excerpt…
  • SEGGER - Florian -

    Replied to the thread Problem disabling bitmap tiling in emWin.

    Post
    Hi, BytesPerLine are calculated as follows: ((BitsPerPixel / 8 * XSize). The bits per pixel depend on the bitmap format. GUI_DRAW_BMPM8888I is a 32bpp format, therefore for your bitmap the BytesPerLine would be ((32 / 8 * 18) = 72. But the data in the…
  • SEGGER - Florian -

    Replied to the thread Problem disabling bitmap tiling in emWin.

    Post
    Hi Josh, A few things are unclear to me. Do you have created the IMAGE widget with the AppWizard? If so, you cannot set a custom callback to that widget, only to widgets created manually with emWin. If the bitmap is just a simple icon, you won't have…
  • SEGGER - Florian -

    Replied to the thread Button press not returning released notification.

    Post
    Hi BMD, Regarding your first question: I am guessing that a press at the edge of a button results in the touch input being moved out of the BUTTON window. When a button is pressed and the touch input is moved out of the window area, the parent window…
  • SEGGER - Florian -

    Replied to the thread WM_SetCallback, unexpected behavior.

    Post
    Hi, WM_SET_CALLBACK gets sent immediately to a window after its callback has been changed by WM_SetCallback(). WM_SetCallback() sends a WM_SET_CALLBACK message before returning the previous function pointer. So your application crashes because the…