What is the qmake command line

Circuits

From the Deployment Guide for the Qt virtual keyboard:

"The integration method is automatically selected by the project files. However, in desktop environments, it is possible to override the desktop integration method and use the application integration method instead, by adding CONFIG+=disable-desktop to the qmake command line."

what exactly is the qmake command line? Where does the line "CONFIG+=disable-desktop" need to be placed in my application?

Gojir4

@circuits Hi,
You need to put this in the project file with suffix .pro

Circuits

Interesting that's where I have it but for some reason these InputFields{} are enabling that top-level keyboard window when they gain focus. If the input field has no setup for the embedded keyboard will the top-level keyboard window appear despite having CONFIG+=disable-desktop in the .pro file?

Currently, in the InputField onActiveFocusChanged I am able to keep it from popping up when clicked by calling the hide() function:

onActiveFocusChanged: {
            Qt.inputMethod.hide()
...

however; this only works if the user does a simple click. If the user double clicks then it appears again. What exactly does CONFIG+=disable-desktop do? Is there any other way I can disable the top-level window? Perhaps from within main.cpp?

Circuits

I believe the answer to my first question is yes. Without having an InputPanel{} setup then regardless if you have CONFIG+=disable-desktop in your .pro file the top-level keyboard window will appear if any TextInput{} gains focus. I am not sure how to keep that from happening, any ideas?

Essentially, I am trying to figure out a way to completely eliminate the top-level keyboard from appearing under any condition but I still want to be able to use the embedded keyboard.

Circuits

@me So I managed to find a larger band-aid then just setting Qt.inputMethod.hide() by instantiating a random InputPanel{visible: false} to accompany the TextField's. This is keeping that top-level window from opening. That being said, there should probobly be a way to completly disable that top-level keyboard window. What are its use cases anyhow? The only time I could see something like that being useful would be if someone broke their desktop keyboard or something...