20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Development
(→Status) |
|||
| Line 174: | Line 174: | ||
== Development == | == Development == | ||
=== Reset/re-init === | |||
{{FGCquote | |||
|1= Once FGPythonSys is able to dynamically shutdown/restart using the corresponding fgcommands, and once it can be entirely disabled during startup, it would already be in a much better shape than 99% of the existing SGSubsystems in FlightGear | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=274199#p274199 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Jan 27th, 2016 | |||
| added = Jan 27th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
=== Subsystems === | |||
{{FGCquote | |||
|1= to make that work, you would need to register a new extension function along the lines of "registerSubsystem()" and "unregisterSubsystem()", which takes a Python class as ist argument that inherits from the equivalent of the SGSubsystem/Mgr parent class, i.e. with init(), update(), reinit() etc methods | |||
The registerSubsystem() API would then look pretty much like what you have added to fg_init.cxx, but you would need to manually/expicitly initialie such classes, because intialization is likely to have completed already by then. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=274234#p274234 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Jan 27th, 2016 | |||
| added = Jan 27th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
== Status == | == Status == | ||