Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

:15 PM To: Qt Interest Subject: Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP? > Ill poke around, Its definitely doable cool, thanks! -dave ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/inter

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

> Ill poke around, Its definitely doable cool, thanks! -dave ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

t when its disengaged? Scott -Original Message- From: Interest On Behalf Of David M. Cotter Sent: Monday, October 25, 2021 2:31 PM To: Qt Interest Subject: Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP? > Ok.. So you want to know when the user "engages" the menubar and

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

> I'm just guessing here, but it might be that the menu bar's events don't get > delivered to the QMainWindow. they do, just not the events i want > Or, perhaps this documented caveat is important: "Note: Events are only > delivered to this event handler if the widget has a native window

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

> Ok.. So you want to know when the user "engages" the menubar and sometime > later when the user "disengages" it. Engagement can come from the keyboard > alt key, or the alt-XXX shortcut for an individual menu. As well as menu > hovering or clicking into any of the menu items. > > Is

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

On Mon, Oct 25, 2021 at 9:40 AM David M. Cotter wrote: > in the documentation here > , it > indicates i can get a message when the menu bar starts to be browsed, and > another when the browsing is completed. > > this is *exactly* what

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

ctober 25, 2021 1:18 PM To: Qt Interest Subject: Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP? > QMenu are just “custom drawn widgets” not native widgets. got it, that explains that. >>> Instead look into QMenu::aboutToShow and QWidget::closeEvent >> does that work for

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

> QMenu are just “custom drawn widgets” not native widgets. got it, that explains that. >>> Instead look into QMenu::aboutToShow and QWidget::closeEvent >> does that work for the ENTIRE menu bar browsing workflow? >> >> ie: get a "start" message when the user clicks the first time in the menu

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

You are mixing and confusing windows native Win32 messages with Qt signals. am I? the doc here for "nativeEvent()" specifically states that this is intended to give you windows messages (WM_*) (on windows) to wit: "receive native platform

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

> You are mixing and confusing windows native Win32 messages with Qt signals. am I? the doc here for "nativeEvent()" specifically states that this is intended to give you windows messages (WM_*) (on windows) to wit: "receive native platform

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

) would only work on Windows, not linux, mac or any other platform. Using Qt's native system will work on all platforms Scott From: Interest On Behalf Of David M. Cotter Sent: Monday, October 25, 2021 9:40 AM To: Qt Interest Subject: [Interest] win: can't trap WM_ENTER/EXITMENULOOP

Re: [Interest] win: can't trap WM_ENTER/EXITMENULOOP?

: Interest on behalf of David M. Cotter Sent: Monday, October 25, 2021 6:39:40 PM To: Qt Interest Subject: [Interest] win: can't trap WM_ENTER/EXITMENULOOP? in the documentation here<https://docs.microsoft.com/en-us/windows/win32/menurc/menus>, it indicates i can get a message when the me

[Interest] win: can't trap WM_ENTER/EXITMENULOOP?

in the documentation here , it indicates i can get a message when the menu bar starts to be browsed, and another when the browsing is completed. this is exactly what i need (the purpose is unrelated to this post). So in my