volodymyr Beginner

  • Member since Jun 13th 2018
Last Activity

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

  • volodymyr -

    Replied to the thread WM_SetUntouchable.

    Post
    Quote from SEGGER - Schoenen: “Hi, OK, now I got it, I guess. Try this: In WM_INIT_DIALOG of _cbDerivedDialog() I create another window which is transparent. This window will catch the input outside _cbDerivedDialog() and do nothing with it. After…
  • volodymyr -

    Replied to the thread WM_SetUserData - issue for widget of DIALOG.

    Post
    Quote from LexaGb: “Hello, WM_GetUserData()/WM_SetUserData() is for simple windows. For widgets just use specific <WIDGET>_GetUserData()/<WIDGET>_SetUserData() functions. In your case it is BUTTON_SetUserData(). Calling WM_SetUserData() for the…
  • volodymyr -

    Posted the thread WM_SetUserData - issue for widget of DIALOG.

    Thread
    Hello, everyone. There is a DIALOG with one BUTTON, that has ExtraBytes. After storing data to the BUTTON-widget with WM_SetUserData the function WM_GetDialogItem for get BUTTON-widget returns 0. Here is source-code: C Source Code (61 lines)
  • volodymyr -

    Replied to the thread WM_SetUntouchable.

    Post
    Quote from SEGGER - Schoenen: “Hi, If I get you right you want to make sure that the initial dialog (the one with _cbDialog) don't receive input when the derived dialog is created (_cbDerivedDialog), right? To achieve that you can simply make the…
  • volodymyr -

    Posted the thread WM_SetUntouchable.

    Thread
    Hello. In v.5.50 there is a new function WM_SetUntouchable(). How to make untouchable some DIALOG or FRAMEWINDOW incl. all its children if I use v.5.38? The answer in my previous thread did not help me (
  • Quote from SEGGER - Schoenen: “Hi, In the callback function of a window which shouldn't be touchable you have to react on WM_TOUCH and forward the message to its parent. Just like: C Source Code (13 lines)Didn't checked it, but it might be necessary…
  • Hello. How to make FRAMEWIN or DIALOG untouchable (insensitive to all mouse/touchpad events including all child-widgets)? I know that Ver. 5.50 already has the function WM_SetUntouchable(). But we are using 5.38.
  • volodymyr -

    Replied to the thread What's the difference between frame,window and dialog.

    Post
    Quote from Ross Lee: “When I design UI with emwin, I find that I can implement my interface with either frame, window or dialog, so my question is what's the difference between these three types? What is the application scenario for each type? Thank…
  • Quote from SEGGER - Schoenen: “Hi all, Unfortunately, there is no API function yet to get the modal window (wondering why..). I will add such a function, but it might take while till it gets released. For now you should use LexasGBs…
  • volodymyr -

    Replied to the thread How to disable reacting the MENU-widget to PID-events (mouse / touchpad)?.

    Post
    Quote from LexaGb: “It seems that "undocumented" message with the code 0x240 is documented. In WM.h it is nothing less than WM_TOUCH! :) ” O, really!! :thumbup: Did not noticed.
  • volodymyr -

    Replied to the thread How to disable reacting the MENU-widget to PID-events (mouse / touchpad)?.

    Post
    Quote from LexaGb: “Yes! Found it too :thumbup: ! But what if they change that undocumented code (0x240) in next releases... :) Why the collapse / expand of MENU widgets is not provided as API functions... ” "But what if they change that undocumented code
  • volodymyr -

    Replied to the thread How to disable reacting the MENU-widget to PID-events (mouse / touchpad)?.

    Post
    Alex, thanks for reply, I will probably think about your solution too.
  • volodymyr -

    Replied to the thread How to disable reacting the MENU-widget to PID-events (mouse / touchpad)?.

    Post
    I already solved this problem!!! 8o 8o 8o There is undocumented internal EmWin message 0x240 (576), that is used for MENU collapse - you should use "break" for this message inside your callback. 8)
  • Hello. There was a following task with special MENU behaviour: If I select the menu-item that is "endpoint" (not a submenu), and press Enter, then new dialog-window should appear, but the entire menu should not collapsed. After closing dialog-window I…