20,741
edits
Canvas PUI mapping: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
* https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/GUI/FGPUIDialog.cxx#l1070 | * https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/GUI/FGPUIDialog.cxx#l1070 | ||
We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets | We will need to come up with some kind of "adapter" class that maps common PUI functionality to arbitrary Canvas widgets, specifically: | ||
* {{tag|height}} and {{tag|width}} | |||
* {{tag|legend}} {{tag|label}} | |||
* {{tag|property}} and {{tag|format}} | |||
* {{tag|binding}} | |||
* {{tag|default}} | |||
* {{tag|visible}} (easy) | |||
* {{tag|keynum}} and {{tag|key}} | |||
* {{tag|font}} | |||
* {{tag|color}} | |||
Currently, this is accomplished in non-generic, fairly roundabout, fashion in the applyPUIAttributes() helper funciton in the pui2canvas parser | Currently, this is accomplished in non-generic, fairly roundabout, fashion in the applyPUIAttributes() helper funciton in the pui2canvas parser | ||