Migrate ShortcutActivator and ShortcutManager to KeyEvent system

APIs provided by the Flutter framework are already migrated. Migration is needed only if you're using any of the methods listed in the previous section.

Migrating your APIs that use ShortcutActivator or its subclasses.

Pass a KeyEvent instead of a RawKeyEvent to ShortcutActivator.accepts. This may mean switching where you get your key events from. Depending on where you get them, this can either mean switching to using Focus.onKeyEvent instead of Focus.onKey, or a similar change if using FocusScope, FocusNode or FocusScopeNode.

If you're using a RawKeyboardListener, switch to using a KeyboardListener instead. If you're accessing RawKeyboard directly, use HardwareKeyboard instead. You'll find that there are non-raw equivalents for all of the key event sources.

Migrating your APIs that extend ShortcutActivator

The ShortcutActivator.accepts method was modified to take a KeyEvent and a HardwareKeyboard instead of a RawKeyEvent and RawKeyboard.

Before:

class MyActivator extends ShortcutActivator {
  @override
  bool accepts(RawKeyEvent event, RawKeyboard state) {
    // ... (your implementation here)
    returns false;
  }
  // ...
}

After:

class MyActivator extends ShortcutActivator {
  @override
  bool accepts(KeyEvent event, HardwareKeyboard state) {
    // ... (your implementation here)
    returns false;
  }
  // ...
}

Migrating your APIs that extend ShortcutManager

The ShortcutManager class was modified to take KeyEvents in handleKeypress instead of RawKeyEvents. One difference in the two APIs is that repeated keys are determined differently. In the RawKeyEvent case, the repeat member indicated a repeat, but in RawKeyEvent code, the event is a different type (KeyRepeatEvent).

Before:

class _MyShortcutManager extends ShortcutManager {
  @override
  KeyEventResult handleKeypress(BuildContext context, RawKeyEvent event) {
    if (event is! RawKeyDownEvent) {
      return KeyEventResult.ignored;
    }
    if (event.repeat) {
      // (Do something with repeated keys.)
    }
    // ... (your implementation here)
    return KeyEventResult.handled;
  }
}

After:

class _MyShortcutManager extends ShortcutManager {
  @override
  KeyEventResult handleKeypress(BuildContext context, KeyEvent event) {
    if (event is! KeyDownEvent && event is! KeyRepeatEvent) {
      return KeyEventResult.ignored;
    }
    if (event is KeyRepeatEvent) {
      // (Do something with repeated keys.)
    }
    // ... (your implementation here)
    return KeyEventResult.handled;
  }
}