20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→2022: https://sourceforge.net/p/flightgear/flightgear/ci/cbd5ef9e7b8f433dbc1ba97bae7d7cfc894e7cef/
m (→2022: https://sourceforge.net/p/flightgear/flightgear/ci/7a0be3f0004fc29c180f858754adc9407b3f1748/tree/src/GUI/PUICompatObject.cxx) |
m (→2022: https://sourceforge.net/p/flightgear/flightgear/ci/cbd5ef9e7b8f433dbc1ba97bae7d7cfc894e7cef/) |
||
| Line 30: | Line 30: | ||
=== 2022 === | === 2022 === | ||
In February 2022, James reported having something in progress locally, and that should even be something we can try in March/April 2022. Hopefully that’s quick enough, knowing it has been a long time coming.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606439/</ref> | In February 2022, James reported having something in progress locally, and that should even be something we can try in March/April 2022. Hopefully that’s quick enough, knowing it has been a long time coming.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606439/</ref> | ||
There's now an XML to Nasal bridge, to keep PUI dialogs working (Disabled by a CMake option) | |||
This builds equivalent C++ objects to what the PUI dialogs build, with properties exposed to Nasal. Peer objects are created by Nasal callbacks, which can implement the various dialog functions needed to keep compatibility, especially the ‘update’ and ‘apply’ hooks.<ref>https://sourceforge.net/p/flightgear/flightgear/ci/cbd5ef9e7b8f433dbc1ba97bae7d7cfc894e7cef/</ref> | |||
Use the following cmake option to enable this code: <code>-DENABLE_PUICOMPAT=ON</code> | |||
The new Compatibility files can now be found in $FG_SRC/GUI: | The new Compatibility files can now be found in $FG_SRC/GUI: | ||