[SOLVED] QLineEdit does not receive character input on Android

[tarod.net]

@SteveMBay Which flag is the "bad guy" here? Qt::Popup or Qt::FramelessWindowHint?

[SteveMBay]

@tarod.net I just wanted to write. :) It isn't a "back & white" situation.

Qt::Popup is the "bad" who prevents to use the QLineEdit but it is the "good" as well, because it allows the background to get input (and this hides my widget). As I've read in the Qt doc other flags prevent the background to get any input.

[tarod.net]

@SteveMBay Sorry, Steve, but I don't understand well the situation.

• When you say "background", you mean another window which is showing your MctMainDialog class?
• The widget you mention, is the MctMainDialog class you showed some days ago?
• You say the widget won't disappear after you touch the surrounding area, but if you detect a touching event, you could hide the widget or window using the functions provided by Qt, couldn't you?

[SteveMBay]

@tarod.net Sorry, my English isn't the best.

• Yes, the "background" is a main window (my application is a text editor) and this widget is like a dropdown menu, where I can setup many things.
• Yes, we are talking the same widget that was QDialog before, but I recreated and now it is a QWidget. (Now called MctWidget, and yes, the name was misleading, it was "main" because it had some child dialogs as well.)
• Maybe :) My (really) main window contains a tool handler object which owns the formatting and configuring dialogs and widgets.

Now I am trying :

1. to override focusInEvent() on this ReallyMainWindow
2. focusInEvent() emits a signal that connected to ToolHandler
3. ToolHandler gets a new slot: where calls this->mctWidget->hide()

[SteveMBay]

@SteveMBay In theory, this should work, but ReallyMainWindow's focusInEvent() never called... :(

[tarod.net]

@SteveMBay Thank you for your answers! :)

Why don't you set MctWidget as modal

setWindowModality(Qt::WindowModal);

and add a button to close this child window?

If you implement that, MctWidget will remain opened until the user clicks the close button, but you will have more control to avoid wrong behaviours.

The line this->setWindowFlags(Qt::Popup| Qt::FramelessWindowHint); should be removed if you like the idea.

About focusInEvent, try with this instead:

bool ReallyMainWindow::event(QEvent *e) {
{
    if (e->type() == QEvent::WindowActivate) {
        // window was activated
    }
    return QWidget::event(e);
}

[SteveMBay]

@tarod.net The Modal window does the trick! Now this works fine! Thank you!

It's so easy solution...

(Otherwise, I don't understand why Qt::Popup prevented to get input. Is this a bug or a feature?)

(About ReallyMainWindow... i found that other view catches the input instead of RMW, and I didn't modify the code so deep, so this was a dead end as well)

[tarod.net]

@SteveMBay When you say that other view catches the input, do you mean other subwindows or child windows which you are using to setup your main window?

In my opinion, it's the same case, and I think you should apply the same solution setting the window modality as Qt::WindowModal.

[SteveMBay]

@tarod.net It isn't so important, but I can explain it.

Other views are the surrounding and background objects on the screen (such as toolbar and docview).

ReallyMainWindow class is just a container, it does not implements the event handling. To be honest, the main structure is not my task and I am not really familiar with the deep details. As far as I see, there are more surface object where the input (touch) can be caught.

 +---ReallyMAinWindow----+
 | toolbar               |
 +-------------+-----+---+
 |             | MCT |   |
 |             +-----+   |
 |    docview            |
 |                       |
 +-----------------------+

[tarod.net]

@SteveMBay As far as I see, ReallyMainWindow wouldn't need to get the inputs. They are needed for the toolbar, MCT and docview, right?

[SteveMBay]

@tarod.net Yes, that's right.
A bit confused me that RMW's base is inherited from QWidget. :) So, technically it's able to get input. But it shouldn't, as you say.

[tarod.net]

@SteveMBay Just for clarification, did you fix the wrong behaviours or do you need more help about this issue?

[tataeress]

a solution i found is to remove only the Qt::Sheet flag and you can let the other Qt::FramelessWindowHint and Qt::Popup with no problem