- 02 Jun, 2021 1 commit
-
-
Anis Alibegić authored
-
- 01 May, 2021 1 commit
-
-
Tong Mu authored
Rewrites tools/gen_keycodes, the script that generates key mappings across the framework and the engine.
-
- 22 Oct, 2020 1 commit
-
-
puelo authored
* Added RawKeyEvent support for iOS * Removed unused remnant * added some missing keys * Removed trailing whitespaces * commit for build * Added mapping names * Made iOS keycodes generatable and collectable * Fixed naming and formatting issues * fixed raw_keyboard_test
-
- 15 Sep, 2020 1 commit
-
-
Greg Spencer authored
Fix the `character` field of the `RawKeyEvent` to hold correct data on non-Android platforms. (#65667) This fixes a problem where the character field of the RawKeyEvent was not being set at all for non-Android platforms. I also updated the key maps, and corrected a problem with the Windows key map where the backquote character wasn't correctly mapped.
-
- 29 Jul, 2020 1 commit
-
-
Tong Mu authored
* Split gen_keycode to make maintenance easier.
-
- 23 Jun, 2020 1 commit
-
-
Robert Ancell authored
-
- 08 Apr, 2020 1 commit
-
-
Francisco Magdaleno authored
-
- 31 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 09 Nov, 2019 1 commit
-
-
Greg Spencer authored
This adds support for the fn key on macOS. It adds it to the key mappings as a supplemental mapping that overwrites the one from the Chrome headers, since the chrome headers have a TODO, but no implementation of the key. Also, ignore the fn key entirely on macOS. This is because On macOS laptop keyboards, the fn key is used to generate home/end and f1-f12, but it ALSO generates a separate down/up event for the fn key itself. Other platforms hide the fn key, and just produce the key that it is combined with, so to keep it possible to write cross platform code that looks at which keys are pressed, the fn key is ignored.
-
- 01 Oct, 2019 1 commit
-
-
Mouad Debbar authored
-
- 16 Apr, 2019 1 commit
-
-
Greg Spencer authored
Updates the keycodes by regenerating them using the script, and fixed a comment in the template to conform to style.
-
- 28 Mar, 2019 1 commit
-
-
Francisco Magdaleno authored
-
- 18 Mar, 2019 1 commit
-
-
Francisco Magdaleno authored
-
- 08 Feb, 2019 1 commit
-
-
Greg Spencer authored
This adds support for logical and physical key information inside of RawKeyEvent. This allows developers to differentiate keys in a platform-agnostic way. They are able to tell the physical location of a key (PhysicalKeyboardKey) and a logical meaning of the key (LogicalKeyboardKey), as well as get notified of the character generated by the keypress. All of which is useful for handling keyboard shortcuts. This PR builds on the previous PR (#27620) which generated the key code mappings and definitions.
-
- 07 Feb, 2019 1 commit
-
-
Greg Spencer authored
This adds a keycode generator that incorporates input from the Chromium and Android source trees, as well as some local tables, to generate static constants for the LogicalKeyboardKey and PhysicalKeyboardKey classes, as well as mappings from each of the platforms we support so far (currently only Android and Fuchsia). This code generator parses the input files, generates an intermediate data structure (`key_data.json`) that is checked in, and then generates the Dart sources for these classes and some static maps that will also be checked in (but are not included in this PR). The idea is that these codes don't change often, and so we don't need to generate them on every build, but we would like to be able to update them easily in the future if new data becomes available. If the existing data disappears or becomes unusable, we can maintain the checked-in data structure by hand if necessary, and still be able to generate the code. This PR only contains the code generator, not the classes themselves. In another follow-on PR, I'll run the generator and check in the output of the generator.
-