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 13:19, 25 February 2017
, 25 February 2017no edit summary
No edit summary |
No edit summary |
||
| Line 95: | Line 95: | ||
|date = Jun 10th, 2016 | |date = Jun 10th, 2016 | ||
|added = Jun 10th, 2016 | |added = Jun 10th, 2016 | ||
|script_version = 0.40 | |||
}}</ref> | |||
It is also worth noting that we don't really need a 1:1 mapping between PUI and Canvas, because we can usually emulate/approximate most PUI widgets rather easily using similar workarounds - as a matter of fact, the whole PUI widget set is rather archaic, and we really only need 2-3 widgets to approximate the full set of supported widgets without much of an effort. | |||
For instance, there are a number of hard-coded widgets, such as the airport-list, waypoint.list or the property browser - under the hood however, all of these end up just being combo/select boxes with items that respond to clicks<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=302709#p302709 | |||
|title = <nowiki> Re: GUI Combo: How to control so it drops down not up </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jan 4th, 2017 | |||
|added = Jan 4th, 2017 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||