1. 25 10月, 2018 2 次提交
  2. 24 10月, 2018 2 次提交
  3. 23 10月, 2018 2 次提交
    • D
      Allow FlutterViewController to specify whether its FlutterView is opaque (#6570) · 427915e2
      Dan Field 提交于
      * Allow FlutterViewController to specify whether its FlutterView is opaque
      427915e2
    • M
      13771 - iOS dictation bug (#6607) · edfe0248
      Matthew Smith 提交于
      According to the iOS docs, implementing
      `- (id)insertDictationResultPlaceholder`
      
      ```Implementation of this method is optional but can be done when you want to provide a specific rectangle for the placeholder animation while the dictation results are being processed. ```
      
      If you do not implement this method, UIKit will insert a default placeholder of 10 whitespace characters. By overriding this, no placeholder text will be inserted. If you implement the `insertDictationResultPlaceholder`, you must implement
      `- (void)removeDictationResultPlaceholder:(id)placeholder willInsertResult:(BOOL)willInsertResult`
      edfe0248
  4. 20 10月, 2018 2 次提交
  5. 19 10月, 2018 1 次提交
  6. 18 10月, 2018 1 次提交
  7. 16 10月, 2018 3 次提交
  8. 13 10月, 2018 4 次提交
  9. 12 10月, 2018 1 次提交
    • J
      Add a callback for iOS when the first Flutter frame is rendered (#6135) · 3ffa3629
      James D. Lin 提交于
      Add a `-[FlutterViewController setFlutterViewDidRenderCallback:]`
      method on iOS so client applications can be notified when the Flutter
      view has rendered.  This can be used for add2app cases to determine
      when to take an initial screenshot for comparisons in automated
      tests.
      
      The callback is expected to be an Objective-C block (or Swift
      closure).  I chose to support only a single callback because it's
      much simpler (especially since it does not require a separate method
      to unregister the callback), and it's not clear that there are use
      cases that would justify additional complexity.  Clients have the
      flexibility to make their callback invoke other callbacks anyway.
      
      I alternatively considered adding a `-[FlutterViewController
      viewDidRenderFirstFlutterFrame]` method that clients could override
      in a subclass, but using an Objective-C block seems more flexible and
      less of a burden.
      
      Fixes https://github.com/flutter/flutter/issues/20665
      3ffa3629
  10. 11 10月, 2018 2 次提交
  11. 10 10月, 2018 1 次提交
  12. 09 10月, 2018 1 次提交
  13. 05 10月, 2018 2 次提交
    • L
      Remove unused imports and variables (#6437) · 90b1023c
      liyuqian 提交于
      This is discovered in the new Google3 checks. It should not block our
      roll but it's nice to fix them.
      90b1023c
    • C
      Remove touch mapper and respect the UITouch phase when calculating the pointer... · 45c5fe56
      Chinmay Garde 提交于
      Remove touch mapper and respect the UITouch phase when calculating the pointer data change type. (#6430)
      
      The touch mapper was a relic of a time when the pointer IDs had to be less
      than 16. Not respecting the touch phase is getting in the way of clients that
      fake their own touches. Turns out the AppDelegate also like to fake touches to
      simulate status bar events. Now, except in cases where there is a specific
      override in place, the UI touch phase is respected.
      45c5fe56
  14. 04 10月, 2018 1 次提交
  15. 03 10月, 2018 1 次提交
  16. 02 10月, 2018 1 次提交
  17. 29 9月, 2018 1 次提交
  18. 28 9月, 2018 2 次提交
  19. 27 9月, 2018 4 次提交
  20. 26 9月, 2018 1 次提交
  21. 25 9月, 2018 4 次提交
  22. 23 9月, 2018 1 次提交
    • C
      Remove the unused Mac Desktop shell. (#6314) · e82db866
      Chinmay Garde 提交于
      This shell used to serve the dual purpose of running Flutter tests as
      well as optionally being able to run Flutter applications on a Mac
      desktop. After all the test runner targets were consolidated
      (flutter_tester), this target was no longer used to run the tests. This
      target is currently only used by engine developers to test changes
      quickly on the host. Even for this purpose, the Desktop embedders are
      more full featured and use the stable embedder API. The presence of a
      cross-platform tester target, alternatives for Desktop targets that use
      the stable embedder API and the fact that this target is no longer
      tested, makes having this code in the source entirely redundant.
      e82db866