1. 26 May, 2021 1 commit
    • Greg Spencer's avatar
      Add iOS key map generation, make macOS var naming consistent with repo (#83146) · 6b087c74
      Greg Spencer authored
      This adds iOS key map generation that uses std::maps. It uses std::maps because on iOS if we use NSDictionaries, then when XCode loads the dylib, the initialization of those status NSDictionaries hasn't yet occurred, and it crashes the app. std::maps have a well-defined static behavior, and are correctly initialized.
      
      I also made the naming of variables, fields, etc. consistent for macOS. We variously had macosFoo, macOSFoo, and macOsFoo. I eliminated macOsFoo and macosFoo, since the rest of the repo uses macOSFoo for lowerCamelCase names (with only a few exceptions). I used iOSFoo for iOS.
      6b087c74
  2. 01 May, 2021 1 commit
  3. 23 Jun, 2020 1 commit
  4. 13 Mar, 2020 1 commit
    • Greg Spencer's avatar
      Add C++ code generation for key maps. (#50998) · 289deef8
      Greg Spencer authored
      This adds generation of some C++ keycode maps for various platforms.
      
      This isn't meant for general use: it's so that the Flutter authors can keep the keycodes up to date with the Chromium and Android (and other) sources. It doesn't run continuously, it's only run occasionally (manually) to update the maps, because they don't change very often, and there is often manual work needed to make it function.
      
      In this PR, I added output of various .cc files that write into an engine repo situated next to the flutter repo on disk. This is a starting point for implementing platform-side handling of key events.
      289deef8