Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

cbracken
Copy link
Member

@cbracken cbracken commented Jan 24, 2021

The current text input manager is win32-specific due to its use of
IMM32. For UWP, we'll need a TSF implementation. Once that happens we'll
want to extract out a TextInputManager interface and add a separate UWP
implementation of this class.

Issues

This is a cleanup patch for #23795 which addressed flutter/flutter#65574: Full IME support for Windows.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt. See testing the engine for instructions on
    writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.
  • The reviewer has submitted any presubmit flakes in this PR using the engine presubmit flakes form before re-triggering the failure.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@google-cla google-cla bot added the cla: yes label Jan 24, 2021
The current text input manager is win32-specific due to its use of
IMM32. For UWP, we'll need a TSF implementation. Once that happens we'll
want to extract out a TextInputManager interface and add a separate UWP
implementation of this class.
Copy link

@clarkezone clarkezone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thx for the change!

@cbracken cbracken merged commit 08daa2c into flutter:master Jan 25, 2021
@cbracken cbracken deleted the win32-textinput branch January 25, 2021 00:22
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Jan 25, 2021
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Jan 25, 2021
zanderso pushed a commit to flutter/flutter that referenced this pull request Jan 26, 2021
* 08daa2c Rename TextInputManager to TextInputManagerWin32 (flutter/engine#23905)

* 611a8d5 Roll Skia from 069e484cc3b9 to 607a382298b2 (1 revision) (flutter/engine#23907)

* aa56ae2 Roll Skia from 607a382298b2 to fe8a4faa4bb2 (4 revisions) (flutter/engine#23910)

* 86e05f0 Roll Fuchsia Linux SDK from mrFdelzNr... to GLRm7LJRm... (flutter/engine#23913)

* 155827a Roll Skia from fe8a4faa4bb2 to bd91660b6e12 (4 revisions) (flutter/engine#23920)

* ef4f5a8 Roll Dart SDK from 2ddf810f71f6 to 70c7daa78288 (1 revision) (flutter/engine#23922)

* 790af8a [macos] Support smooth resizing for Metal (flutter/engine#23924)

* 2707c21 use a single clang toolchain (flutter/engine#23842)

* 523c8c8 Adds a mechanism for announce events to be forwarded to a11y. (flutter/engine#23499)

* ee07d1b Roll Skia from bd91660b6e12 to fff4099358bd (9 revisions) (flutter/engine#23929)
hjfreyer pushed a commit to hjfreyer/engine that referenced this pull request Mar 22, 2021
The current text input manager is win32-specific due to its use of
IMM32. For UWP, we'll need a TSF implementation. Once that happens we'll
want to extract out a TextInputManager interface and add a separate UWP
implementation of this class.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants