Relatedly, there have been general conversations several times in the past about the need for a formal keyboard API in embedding.h, rather than passing text input and key events via a platform channel.

b/140830852

I have a Wayland Embedder client working with the exception of Keyboard. I send key events, and they're dropped by the engine. It looks like I need to modify the Engine to register a "flutter/keyevent" handler. Will this change enable a default channel in the embedder for keyevents?

It looks like I need to modify the Engine to register a "flutter/keyevent" handler.

The listener is in the framework code, and is always present. You should not need to modify the engine.

Will this change enable a default channel in the embedder for keyevents?

No (per above), but it will provide an explicit API in embedder.h that embedders should use instead of the message channel.

IIRC, someone were experimenting on merging Platform Runner & UI Runner.

Would it be another option?

This was fixed by the various delayed key event changes. Closing.

This can be moved to "Done" in project "Desktop Features", right?

@nilsux Yes, done. Thanks.

I have a Wayland Embedder client working with the exception of Keyboard. I send key events, and they're dropped by the engine. It looks like I need to modify the Engine to register a "flutter/keyevent" handler. Will this change enable a default channel in the embedder for keyevents?

Sorry to bump an old issue, but I'm having the same problem with this comment and I'm not sure where to ask.

I have successfully embedded Flutter in my OpenGL app using software renderer, using the official 2.0.1 build (using official artifacts from the wiki page. Rendering & mouse/pointer events works fine. However, I'm not able to send or receive any platform messages to/from the flutter engine:

• The FlutterProjectArgs.platform_message_callback is never called, and
• sending keyboard events via flutter/keyevent has no effect (I implement something similar to the glfw key handler)

Also if I use a native plugin, if I invoke MethodChannel from Flutter/Dart side, it never returns.

For the project args, I only filled assets_path, icu_data_path & platform_message_callback, and the rest I leave to the default values.

Are there other prerequisites for communication with flutter using platform messages?

Thanks!

@siavee That has nothing to do with this issue. Most likely you aren't servicing the engine tasks (either by providing a platform task runner, or regularly calling the deprecated __FlutterEngineFlushPendingTasksNow).

If that's not it, you should either file a new issue or use a resource like StackOverlfow or Discord, since this issue was about adding specific new functionality for key events.

@stuartmorgan Thanks for the response! That's probably it, I'll try providing a task runner and I'm very sorry about the noise.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.