Posting a QKeyEvent to a QLineEdit

[jpn]

QLineEdit uses QKeyEvent::text() for inserting text.

QApplication::postEvent(_line_edit,
                            new QKeyEvent(QEvent::KeyPress,
                                          Qt::Key_A,
                                          Qt::NoModifier,
                                          "a")); // <-QKeyEvent::text

QApplication::postEvent(_line_edit,
                            new QKeyEvent(QEvent::KeyPress,
                                          Qt::Key_A,
                                          Qt::NoModifier,
                                          "a")); // <-QKeyEvent::text

To copy to clipboard, switch view to plain text mode 

[wysota]

Can't you simply use QLineEdit::setText() or QLineEdit::insert()?

[cocheci]

Can't you simply use QLineEdit::setText() or QLineEdit::insert()?

I could have, but I was just wondering why the posting of the key press event does not work.
My next question is why posting a QMousePress event to the QLineEdit doesn't do the same thing as it does when run interactively (i.e. set the keyboard focus on the QLineEdit).

Thanks,
Cristian

[wysota]

Because it is QFocusEvent's responsibility.

[jpn]

It's the OS which is responsible for sending appropriate events. There are separate mouse and focus in/out events. A single mouse event doesn't cause all other appropriate events to be sent (compared to the situation what happens upon a mouse click).

QWidget offers methods for setting focus and QLineEdit (or QTextCursor) offers methods for setting cursor position. Don't try to re-invent a wheel..

[cocheci]

It's the OS which is responsible for sending appropriate events. There are separate mouse and focus in/out events. A single mouse event doesn't cause all other appropriate events to be sent (compared to the situation what happens upon a mouse click).

QWidget offers methods for setting focus and QLineEdit (or QTextCursor) offers methods for setting cursor position. Don't try to re-invent a wheel..

Because it is QFocusEvent's responsibility.

But ... here's what I'm trying to achieve: I am trying to write automatic unit tests for my widgets by "simulating" the user interaction with the widget. E.g. for a left mouse press I am sending a MousePress event to the widget. Are you saying that's not enough? Are you saying that I cannot automate the simulation of the user interaction with the widget?

[jacek]

Are you saying that I cannot automate the simulation of the user interaction with the widget?

You can, but you have to send all events that normally would be sent to that widget. You could use event filter to record all events and then just replay them.

[cocheci]

You can, but you have to send all events that normally would be sent to that widget. You could use event filter to record all events and then just replay them.

I tried that, but it didn't quite work as in interactive mode. The LineEdit receives 4 events when the user clicks on it:

Enter
FocusIn
MousePress
MouseRelease

When I send these four events to the line edit, the bliking cursor is displayed (in the LineEdit), but the LineEdit never receives the keyboard focus. I even sent a FocusOut event to the widget that is supposed to lose focus, but the LineEdit still didn't gain focus.

Thanks,
Cristian

[jpn]

Looks like it might be impossible to handle it this way. Still if you send a focus event and the widget even receives it, QApplication won't be tricked. Although the widget prepares itself as if it had been focused (like QLineEdit's cursor starts blinking etc.), the next (real) key press event still goes to a widget which the qApp believes that has focus. QApplication updates it's focus widget (QApplicationPrivate::setFocusWidget()) only when a focus event comes from the underlying system, window manager, or focus is set manually by calling QWidget::setFocus().

[jacek]

Maybe you could use QtTest module? It has some methods for sending key events.

[cocheci]

Maybe you could use QtTest module? It has some methods for sending key events.

Thanks Jacek, it looks like this might work, I'll definitely try it. Here's the first phrase from the "Simulating GUI Event" chapter:

QTestLib features some mechanisms to test graphical user interfaces. Instead of simulating native window system events, QTestLib sends internal Qt events. That means there are no side-effects on the machine the tests are running on.

If this works, I'll let you know.

Cristian

[cocheci]

Thanks Jacek, it looks like this might work, I'll definitely try it. Here's the first phrase from the "Simulating GUI Event" chapter:

QTestLib features some mechanisms to test graphical user interfaces. Instead of simulating native window system events, QTestLib sends internal Qt events. That means there are no side-effects on the machine the tests are running on.

If this works, I'll let you know.

Cristian

This worked, thank you all!!

Cristian