End-User acknowledges that the Agreement is concluded solely between OEM and End-User, and not with Jeppesen GmbH and/or Jeppesen Sanderson Inc. In case of a conflict between the Agreement and anything stated in these Additional Terms, these Additional Terms shall govern and prevail.Ī. ANY USE OF THE PRODUCTS WILL ALSO CONSTITUTE YOUR AGREEMENT WITH THESE ADDITIONAL TERMS AS PART OF THE AGREEMENT. BY YOUR BELOW SIGNATURE, END-USER IS AGREEING TO EACH TERM OF THESE ADDITIONAL TERMS AS PART OF THE AGREEMENT INCLUDING THE RESTRICTIONS ON USE, DISCLAIMERS AND LIMITATION OF LIABILITIES. THESE ADDITIONAL TERMS ARE LEGALLY BINDING UPON YOU IN ADDITION AND AS AN INTEGRAL PART OF THE AGREEMENT. PLEASE READ THE FOLLOWING ADDITIONAL TERMS (“Additional Terms”) PROVIDED TO YOU BY OEM CAREFULLY BEFORE USING THE PRODUCTS. Old plugins will continue to function, and you could even write new plugins and compile them against the old API (I’m not sure why you would you want to…), and they’ll work in X-Plane 11.10 and beyond.Additional Terms for Jeppesen DataYOU (herein also “End-User”) HAVE LICENSED JEPPESEN’S NAVDATA (“DATA”) (called “Products” hereinafter) FROM NAVIGRAPH KB (“OEM”) UNDER AN AGREEMENT (herein “Agreement”). Just to be 100% clear, to get any of these features (with the exception of the backward-compatibility wrapper for instanced drawing, of course), you’ll need to compile against the XPLM300 API.
X plane 11 key binds windows#
X plane 11 key binds for free#
Support for automatic UI scaling of all drawing in your window (this comes for free in all windows created with XPLMCreateWindowEx that are compiled against the XPLM300 API)-this means users with hi-DPI/4k monitors who have set a 150% or 200% scale for the X-Plane UI will get the experience they do with built-in windows.Support for “popping out” windows into first-class OS windows (demoed in the same sample project above).Support for styling windows like the built-in X-Plane 11 windows (sample project here).Lots and lots of new features for plugin-created UI in the XPLMDisplay API, including:.More joystick axes & buttons, to match X-Plane 11.10’s support for 20 USB devices (up from the previous cap of 10).When you add a menu item via XPLMAppendMenuItemWithCommand(), if the user has a key bound to that command, the key will be displayed on the right-hand side of the menu, just like X-Plane’s native menus. Menu items that show keyboard shortcuts.Plugins that get loaded with the user’s aircraft will now have access to XPLMFindAircraftMenu(), to which you can append new menu items or submenus. Two minor features for menus (in the XPLMMenus API see the new menu SDK sample for examples):.Based on our RFC, this provides an interface for drawing text labels, PNG icons, and arbitrary OpenGL within the X-Plane 11 maps. Map APIs (via the new XPLMMap header).Using the wrapper, you don’t get the performance benefit that you’d see in X-Plane 11, but you’ll at least be able to use the same API. The good news for developers still working on X-Plane 10 plugins is that we’ve created a “ wrapper” to provide backward compatibility with old versions of the SDK. More info on the theory behind this in Ben’s recent post. This is a really important one for improving plugin drawing performance. Instanced drawing (via the new XPLMInstance header).There are a handful of really important features here for plugin developers:
X plane 11 key binds code#
But, that doesn’t mean you can’t look at the code itself right now! NB: The code samples linked below will not work yet-in part because X-Plane 11.10 isn’t in beta yet, and in part because we haven’t updated the sample code downloads with the new XPLM300 headers. The upcoming X-Plane 11.10 release (and before you ask, we’ll let you know as soon as we have an ETA! 🙂 ) will include Version 3.0 of the X-Plane SDK (XPLM).
0 kommentar(er)
