4 Commits

Author	SHA1	Message	Date
Chinmay Garde	99ee3c2b0d	Provide a placeholder queue ID for the custom embedder task runner. (#11062) ... This issue would only manifest when a custom task runner was being used with a custom compositor. Both were tested separately but not together. A new test has been added for this. We still create the GPU thread merger unnecessarily but I can patch that later. I also cleaned up the existing custom task runner test to not submit tasks on a dead engine as they just log errors unnecessarily. Filed new: https://github.com/flutter/flutter/issues/38844	2019-08-19 15:56:58 -07:00
Chinmay Garde	96a1a843cb	Replace lock_guard with scoped_lock and use class template argument deduction. (#9338)	2019-06-17 10:08:45 -07:00
Chinmay Garde	56052c70af	Rename the shell namespace to flutter. (#8520)	2019-04-09 17:10:46 -07:00
Chinmay Garde	cb8eb801a4	Allow embedders to specify their own task runner interfaces. (#8273) ... Currently, all Flutter threads are managed by the engine itself. This works for all threads except the platform thread. On this thread, the engine cannot see the underlying event multiplexing mechanism. Using the new task runner interfaces, the engine can relinquish the task of setting up the event multiplexing mechanism and instead have the embedder provide one for it during setup. This scheme is only wired up for the platform thread. But, the eventual goal is to expose this message loop interoperability for all threads.	2019-03-27 16:16:59 -07:00