20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 16:02, 9 October 2016
, 9 October 2016→Is this going to be committed ?
| Line 577: | Line 577: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref>, i.e. the status is that since there has not been a fundamental objection against this on the mailing list and several people have said they can live with the option as long as it remains an option, ThorstenR offered to commit pui2canvas to FGData in the form of a Nasal module that gets loaded 'on demand' dependent on a set property (similar to AW). | }}</ref>, i.e. the status is that since there has not been a fundamental objection against this on the mailing list and several people have said they can live with the option as long as it remains an option, ThorstenR offered to commit pui2canvas to FGData in the form of a Nasal module that gets loaded 'on demand' dependent on a set property (similar to AW). | ||
We'll then see whether people find it more widely useful etc. and whether FG more generally relies on it for fixing | We'll then see whether people find it more widely useful etc. and whether FG more generally relies on it for fixing certain PUI bugs/issues or not.<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=289910#p289910 | |url = https://forum.flightgear.org/viewtopic.php?p=289910#p289910 | ||
|title = <nowiki> Re: canvas vs. on-screen messages - 1:0 </nowiki> | |title = <nowiki> Re: canvas vs. on-screen messages - 1:0 </nowiki> | ||