20,741
edits
Canvas ND framework: Difference between revisions
Jump to navigation
Jump to search
m
→Development: http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=214897#p214835
m (fix usage of git link template) |
m (→Development: http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=214897#p214835) |
||
| Line 354: | Line 354: | ||
== Development == | == Development == | ||
=== Getting rid of Aircraft Dependencies === | |||
* the constructor/newMFD() methods still contain a few hard-coded assumptions due to the origins of the code, but those can be also moved into some kind of construct() field in the hash, or you can simply use the method I suggested, i.e. hiding unneeded symbols. But you're right, that the most proper solution would be identifying non-generic code that contains hard-coded assumptions and moving that into some kind of construct() field that is simply invoked by the new/newMFD() methods. Doing that would not be difficult, it would be just copy & paste - i.e. copy from the navdisplay.mfd file into the style file, by adding a corresponding hash field entry there - and calling it instead. Takes under 3 minutes[http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=214897#p214835] | |||
=== Encapsulating Properties === | === Encapsulating Properties === | ||
{{FGCquote | {{FGCquote | ||