20,741
edits
No edit summary |
mNo edit summary |
||
Line 98: | Line 98: | ||
}}</ref> | }}</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. | 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 additional Canvas 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 | 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 | |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> | |title = <nowiki> Re: GUI Combo: How to control so it drops down not up </nowiki> |