|
From: Stuart B. <stu...@gm...> - 2018-01-05 16:50:46
|
Hi All, Over the Christmas break I've been doing some further work on the FG1000 implementation. Key changes are: 1) Using Emesary to link between the MFD and underlying simulation state. This should make it easy to run the MFD on a separate FG instance, and provides a good demarkation between the individual aircraft systems and the FG1000 itself. 2) Create various underlying classes to support UI features - highlighting, editing. The idea here is that one can create the UI as an SVG file, and these are used to control it. For an example of this in use, see the Airport Information page. Press the CRSR knob to create a cursor on the ICAO airport ID, then use the inside FMS knob to start editing the ID. This should make creating most of the rest of the pages far easier. See http://wiki.flightgear.org/Canvas_MFD_Framework for details of the elements now supported. There's still a huge number of pages to write, and the pages around route planning will likely be particular "fun", but it should be far faster now these blocks are in place. The FG1000 wiki page (http://wiki.flightgear.org/FG1000) shows the pages that have been created so far (4 out of 28!). I'm pretty happy with the overall architecture now, so if anyone wants to create some of the pages they are very welcome to do so! -Stuart |