![]() Some properties are so called tied properties which are directly mapped to internal C++ variables and they cannot be modified using the property browser, we are currently trying to get rid of tied properties, see Howto:Use_Property_Tree_Objects for details. Whole tied property aspect of the api could go away and the property system So without looking deep into how muchĮffort/change/impact this would require, I think for the most part the Performance and use of global structures. Early property system skepticism included issues like Coders couldĬontinue to use native compiled variables and simultaneously expose them to "hypothetical" performance concerns in the early days. Tied properties Note The origin of tied properties was largely to address See $FG_ROOT/Nasal/prop_key_handler.nas for more information. This method also features tab-completion similar to bash: it will cycle through a list of existing properties that match what has been typed already. fdm/jsbsim) and type : to open the property browser at that path or ! to display it in the list of properties. The browser allows you to inspect and even change values in the live running copy of FG.Īlternatively, if you have enabled the corresponding "development extension" (see the menu item in the Debug menu), after typing / you can type in a path (e.g. Just about everything interesting/useful is published in the property system. Through the main menu: Debug > Browse Internal Properties (in older version: File > Browse Internal Properties).īrowse around to see the different data fields that are available.The property browser can be opened while FlightGear is running either: 5.3 Displaying On-Screen property values through nasal.5.2 Opening the property browser through nasal. ![]() 5.1 Forcing open the browser on startup.5 Other ways to open the property browser. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |