Talk:FlightGear version check: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
Line 1: | Line 1: | ||
== features == | == features == | ||
== GUI independent == | === localized === | ||
should use $FG_ROOT/Translations as a workaround for non-English errors messages | |||
=== GUI independent === | |||
{{FGCquote | {{FGCquote | ||
|1= It should also be GUI independent (i.e. it works in a non-GUI mode with no PUI, no Phi, no Canvas, no Qt, etc.). | |1= It should also be GUI independent (i.e. it works in a non-GUI mode with no PUI, no Phi, no Canvas, no Qt, etc.). |
Revision as of 16:48, 17 November 2015
features
localized
should use $FG_ROOT/Translations as a workaround for non-English errors messages
GUI independent
It should also be GUI independent (i.e. it works in a non-GUI mode with no PUI, no Phi, no Canvas, no Qt, etc.). — bugman (Nov 17th, 2015). Re: version checking for matching fgfs and -set.xml files.
(powered by Instant-Cquotes) |
logprint
should be used to ensure that everything shows up in the log file
properties
we could make this much more generic by allowing arbitrary properties to be checked and warnings/errors to be shown, which would allow aircraft developers to provide custom messages to clarify if/how an aircraft is going to be affected by mismatching versions--Hooray (talk) 08:33, 17 November 2015 (EST)
conditions
props.nas