This isn’t a big deal right now-after all, if you’ve installed payware, you probably already own the sim anyway-but it will be a shame if, in The Glorious Future™, you have to choose between your payware and core X-Plane functionality. And, since some plugins (like the ones used in the new Flight Factor A320 Ultimate) depend on a version of CEF provided by a (global) plugin, we have to disable X-Plane’s web browser functionality in the presence of that plugin. There’s not a good way to load two copies of CEF at a time. While its present use is quite limited, if all goes well, we’d like to expand its use elsewhere in the sim-in The Glorious Future™, we could potentially use it to load online charts and the like.
The web view is seamless-you can’t tell by looking at the app that it’s not just part of the native X-Plane user interface.
Cef chrome full version#
We’re using the Chromium Embedded Framework (CEF)-essentially the same guts as Chrome, wrapped inside X-Plane.įor the time being, it’s being used in one place only *: to support in-app upgrades, so that if you have the demo, you can buy the full version of X-Plane without having to go to the web site. More.In the X-Plane 11.20b1, we’re shipping a web browser for the first time. More.Ĭomma delimited list of schemes supported by the associated CefCookieManager. More.Ĭomma delimited ordered list of language codes without any whitespace that will be used in the "Accept-Language" HTTP header. More.īackground color used for the browser before a document is loaded and when no document color is specified. The number of stack trace frames to capture for uncaught exceptions. Set to a value between 105 to enable remote debugging on the specified port. Set to true (1) to disable loading of pack files for resources and locales.
The fully qualified path for the locales directory. The fully qualified path for the resources directory. More.Ĭustom flags that will be used when initializing the V8 JavaScript engine. The directory and file name to use for the debug log. The locale string that will be passed to WebKit. Value that will be inserted as the product portion of the default User-Agent string. Value that will be returned as the User-Agent HTTP header. To persist user preferences as a JSON file in the cache path directory set this value to true (1). To persist session cookies (cookies without an expiry date or validity interval) by default when using the global cookie manager set this value to true (1). The location where user data such as the Widevine CDM module and spell checking dictionary files will be stored on disk. The root directory that all CefSettings.cache_path and CefRequestContextSettings.cache_path values must have in common.
The location where data for the global browser cache will be stored on disk. Set to true (1) to disable configuration of browser process features using standard CEF and Chromium command-line arguments.
Set to true (1) to enable windowless (off-screen) rendering support. Set to true (1) to control browser process main (UI) thread message pump scheduling via the CefBrowserProcessHandler::OnScheduleMessagePumpWork() callback. Set to true (1) to have the browser process message loop run in a separate thread. Set to true (1) to enable use of the Chrome runtime in CEF. The path to the CEF framework directory on macOS. The path to a separate executable that will be launched for sub-processes. Set to true (1) to disable the sandbox for sub-processes.
0 kommentar(er)
