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

Ok.. here is what I came up with  https://github.com/scottaronbloom/SABUtils/blob/master/MenuBarEx.cpp and https://github.com/scottaronbloom/SABUtils/blob/master/MenuBarEx.h Simply promote your menuBar in QtDesigner to CMenuBarEx or instantiate it rather than QMenuBa if you create the

Re: [Interest] QDir().rename() or QFile::rename() on Android 11

On Monday, 25 October 2021 05:37:06 PDT maitai wrote: > It works perfectly on Android 9 (cannot test on Android 10), but fails > miserably on Android 11. Can you let me know what kernel versions those two systems have? Qt uses a different system call for renaming in kernels 3.16 and later. Your

Re: [Interest] bulding Qt from git

On Sunday, 24 October 2021 06:26:25 PDT Cristian Adam wrote: > You can configure with -skip qtpositioning in case you don't need the > qtpositioning Qt Module. Recommend -skip qtlocation since that one isn't in release quality yet, whereas qtpositioning is. -- Thiago Macieira - thiago.macieira

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?

Ill poke around, Its definitely doable, but I don’t know any "trivial" about to engage, or disengage with the menubar. Since its always visible and doesn’t close, that’s clearly not what you want. Can I ask, what is the goal? As in, what do you do when its activated? What about when its

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?

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 this correct

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?

You are mixing and confusing windows native Win32 messages with Qt signals. You are making the incorrect assumption that the Qt core internals are based on Windows native widgets. That is your mistake. Instead look into QMenu::aboutToShow and QWidget::closeEvent Your solution (if it worked)

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

QMenuBar is not a Win32 native menu bar, and neither is QMenu backed by a native win32 menu. Windows knows nothing about their role in the UI (unless it asks for it via accessibility infrastructure, but that’s unrelated to those messages). Volker From:

[Interest] Javascript: export class?

Hello, Can I use a class defined in another .js file? I.e. class A defined in a.js file. I want to define another B class in b.js which will be extending A class. I load these files using such code: QJSEngine::evaluate(afile.readAll(), afile.fileName()); QJSEngine::evaluate(bfile.readAll(),

[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

Re: [Interest] debugging source fail? (windows, qt6)

indeed that was the issue! for those just tuning in, calling "windeployqt" with the "--pdb" option did the trick. -dave > On Oct 25, 2021, at 1:37 AM, Alexandru Croitor > wrote: > > Hi, > > From the 'bad' screenshot, it appears that the .pdb files are not picked up. > Source mappings

Re: [Interest] bulding Qt from git

Final three conclusions of this resolved thread:   1.) I learned that the dev branch is not necessarily stable. In this case Qt staff is working on qtpositioning and when trying to build the dev branch one needs to -skip qtpositioning in the confguation process.   2.) cmake config messages are

[Interest] QDir().rename() or QFile::rename() on Android 11

Hi, I need to move globally one folder to another in /Android/Data/myapp/files. App is built against SDK29, and I do have android:requestLegacyExternalStorage="true" in the manifest. I am using QFile::rename, or QDir().rename() with same bad result when running Android 11. There is no

Re: [Interest] debugging source fail? (windows, qt6)

Hi, From the 'bad' screenshot, it appears that the .pdb files are not picked up. Source mappings don't affect lookup of pdb files as far as i i know. If you mouse hover over one of the gray QFileInfo rows, what does the QtCreator popup say? Perhaps when you run your application, you've already

Re: [Interest] Are there limits to the number of vertices that can be allocated on a QSGGeometry?

Laszlo, Thanks for your reply. I’ve tried to set indexType as UnsignedIntType but it made no difference what so ever. I’m wondering why does it make no difference. Is this explainable in any way? I guess we will need to proceed with the splitting… Thanks! Nuno > On 21 Oct 2021, at 09:44,