- 07 2月, 2020 1 次提交
-
-
由 George Wright 提交于
This also adds a dependency on SwiftShader's Vulkan frontend.
-
- 25 1月, 2020 1 次提交
-
-
由 George Wright 提交于
This paves the way for us to have shell_unittests backed by different rendering APIs (e.g. OpenGL, Vulkan, Metal).
-
- 19 12月, 2019 2 次提交
-
-
由 Kaushik Iska 提交于
This reverts commit 6ea69a0d. On top of the revert, it reverted a commit in the PR: https://github.com/flutter/engine/pull/14024 This reverts commit ea67e5b0b930ebf552bc7dbd678a35ee6a129c39.
-
由 Kaushik Iska 提交于
This reverts commit d117ac97.
-
- 14 12月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
This is a non-breaking addition to the stable Flutter Embedder API and exposes a subset of the functionality provided by Dart_PostCObject API in a stable and tested manner to custom embedder implementations. Send port acquisition can currently be done as described in the unit-test but there may be opportunities to extend this API in the future to access ports more easily or create ports from the native side. The following capabilities of the the Dart_PostCObject API are explicitly NOT exposed: * Object arrays: This allows callers to create complex object graphs but only using the primitives specified in the native API. I could find no current use case for this and would have made the implementation a lot more complex. This is something we can add in the future if necessary however. * Capabilities and ports: Again no use cases and I honestly I didn’t understand how to use capabilities. If needed, these can be added at a later point by appending to the union. Fixes https://github.com/flutter/flutter/issues/46624 Fixes b/145982720
-
- 13 12月, 2019 2 次提交
-
-
由 Kaushik Iska 提交于
This gives us a time closer to when the frame will be rendered on screen. Fixes: https://github.com/flutter/flutter/issues/10850
-
由 Kaushik Iska 提交于
This makes it so that the platform views can be passed an arbitraty CreateVsyncWaiter callback that lets us inject a vsync waiter other than just the simulated monotonic vsync waiter that currently exists.
-
- 05 12月, 2019 1 次提交
-
-
由 David Worsham 提交于
* Remove erroneous ChildView opacity * Wire frame metrics through contexts * Maintain layer stack inside of SceneBuilder * Remove EnsureSingleChild * Centralize system-composite and elevation logic * Wire up OpacityLayer to Scenic
-
- 27 11月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
The converters are still in a separate target that must be included manually. This allows targets that depend on FML but not Dart runtime not have to depend on the runtime. Adds a test that includes this target and tests image decompression from assets. There is also a test for the standalone DartConvertor in shell_unittests but not in fml_unittests be cause FML uni-tests cannot yet launch a VM. I will work on adding fixtures for those.
-
- 21 11月, 2019 1 次提交
-
-
由 George Wright 提交于
This ensures we rasterize into the canvas passed in as subclasses may reimplement AcquireFrame in different ways that don't utilize the canvas object passed in (such as Fuchsia's flutter_runner::CompositorContext).
-
- 19 11月, 2019 1 次提交
-
-
由 Todd Volkert 提交于
This reverts commit f456423c. This is being reverted because it caused flutter/flutter#45098 (images don't load on iOS).
-
- 15 11月, 2019 1 次提交
-
-
由 Chris Yang 提交于
-
- 02 11月, 2019 1 次提交
-
-
由 Dan Field 提交于
-
- 23 10月, 2019 3 次提交
-
-
由 gaaclarke 提交于
-
由 Chinmay Garde 提交于
Investigation is tracked in https://github.com/flutter/flutter/issues/43192
-
- 22 10月, 2019 1 次提交
-
-
由 gaaclarke 提交于
-
- 18 10月, 2019 1 次提交
-
-
由 George Wright 提交于
This re-enables thread safety checks for WeakPtr. WeakPtrs can't be used on a thread other than the one the WeakPtrFactory was created on. This fixes the unit tests and adds a getUnsafe() method to WeakPtr to work around the remaining unresolved locations where we are using WeakPtr unsafely.
-
- 11 10月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
Since this is currently only meant to be used by the embedding internally, the setter in Objective-C is only exposed via the FlutterDartProject private class extension. Unit tests have been added to the shell_unittests harness. Fixes https://github.com/flutter/flutter/issues/37641
-
- 09 10月, 2019 1 次提交
-
-
由 Chris Yang 提交于
Texture unregistration is finished on the GPU thread. The FlutterTexture implementation might not know when it is finished which leads to a race condition. Adding this callback so the FlutterTexture is aware of end of the unregistration process.
-
- 28 9月, 2019 1 次提交
-
-
由 Jonah Williams 提交于
-
- 24 9月, 2019 1 次提交
-
-
由 chunhtai 提交于
* Add windows font change logic * update * fix comment
-
- 24 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
We will end up creating fewer threads in tests.
-
- 17 8月, 2019 1 次提交
-
-
由 Shi-Hao Hong 提交于
* Pass Android Q system gesture inset information from insets.systemGestureInsets to Window.systemGestureInsets
-
- 09 8月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 06 8月, 2019 2 次提交
-
-
由 Chinmay Garde 提交于
The rasterizer may only be accessed safely on the GPU task runner. The test was accessing the same on a non-engine known task runner instead (i.e the tests main task runner). Crashes previously reproducible on all platforms with the following filters: `--gtest_filter="*ShellTest.SetResourceCacheSize*" --gtest_repeat=-1 --gtest_shuffle --gtest_random_seed=1988` at run ~400. Fixes https://github.com/flutter/flutter/issues/37629
-
由 Dan Field 提交于
-
- 03 8月, 2019 1 次提交
-
-
由 Dan Field 提交于
-
- 11 7月, 2019 1 次提交
-
-
由 gaaclarke 提交于
Got rid of the black frame by synchronizing the main thread with the gpu thread to make sure a frame is rendered before presenting the view.
-
- 25 6月, 2019 1 次提交
-
-
由 liyuqian 提交于
For https://github.com/flutter/flutter/issues/34867 Test added: * ReportTimingsIsCalledImmediatelyAfterTheFirstFrame
-
- 21 6月, 2019 1 次提交
-
-
由 Jason Simmons 提交于
-
- 19 6月, 2019 1 次提交
-
-
由 liyuqian 提交于
Had change locally but forgot to `git commit -a` before `git push`...
-
- 12 6月, 2019 2 次提交
-
-
由 liyuqian 提交于
This should satisfy the low-latency need of DevTools. Test added: * ReportTimingsIsCalledSoonerInNonReleaseMode * ReportTimingsIsCalledLaterInReleaseMode
-
由 Chinmay Garde 提交于
-
- 08 6月, 2019 1 次提交
-
-
由 Ben Konyi 提交于
-
- 07 6月, 2019 1 次提交
-
-
由 liyuqian 提交于
Using it, a Flutter app can monitor missing frames in the release mode, and a custom Flutter runner (e.g., Fuchsia) can add a custom FrameRasterizedCallback. Related issues: https://github.com/flutter/flutter/issues/26154 https://github.com/flutter/flutter/issues/31444 https://github.com/flutter/flutter/issues/32447 Need review as soon as possible so we can merge this before the end of May to catch the milestone. Tests added: * NoNeedToReportTimingsByDefault * NeedsReportTimingsIsSetWithCallback * ReportTimingsIsCalled * FrameRasterizedCallbackIsCalled * FrameTimingSetsAndGetsProperly * onReportTimings preserves callback zone * FrameTiming.toString has the correct format This will need a manual engine roll as the TestWindow defined in the framework needs to implement onReportTimings.
-
- 05 6月, 2019 1 次提交
-
-
由 Ben Konyi 提交于
* Allow for whitelisted flags to be passed to the Dart VM Fixed part of https://github.com/flutter/flutter/issues/32176
-
- 21 4月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-
- 20 4月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
The callbacks can be wired in via the Settings object. Both runtime and shell unit-tests have been patched to test this.
-
- 19 4月, 2019 1 次提交
-
-
由 Chinmay Garde 提交于
-