20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→Canvas Emulation: https://sourceforge.net/p/flightgear/mailman/message/37805176/
m (→Canvas Emulation: https://sourceforge.net/p/flightgear/mailman/message/37805060/) |
m (→Canvas Emulation: https://sourceforge.net/p/flightgear/mailman/message/37805176/) |
||
| Line 103: | Line 103: | ||
* Grid layout | * Grid layout | ||
** GridLayout needs debugged: After this, the basic UI is usable, would probably make it a switchable option on ‘next’ (I can already use the simulator with the new UI today, but all the sizes are off in the grid layouts which we use everywhere) | |||
* list | * list | ||
* table (and tree ?) models corresponding views | * table (and tree ?) models corresponding views | ||
* waypoint list | * waypoint list | ||
* log list | * Re-write the waypoint list and airport dialog to work again (since these use custom widgets): | ||
* airport-list equivalents | ** log list | ||
** airport-list equivalents | |||
* Nasal access to the menu i18n functions | * Nasal access to the menu i18n functions | ||
* selection support for single- and multi-line text (which is being worked on -> CanvasPangoText) | * selection support for single- and multi-line text (which is being worked on -> CanvasPangoText) | ||
* Keyboard shortcut handling, although this is not really a PUI vs replacement issue, to me we should handle UI shortcuts in the same was normal keyboard.xml shortcuts | |||
** this previously worked because PUI got ‘first chance’ at handling key input. But we always had duplication between keyboard.xml and other places, so I would rather standardise on keyboard.xml, but allow a UI element to set a scope for shortcuts. (So that Copy/paste shortcuts etc can work in a text input, at least … but probably some other standard ones) <ref>https://sourceforge.net/p/flightgear/mailman/message/37805188/</ref> | |||
* Ensure all the places which use the PUI combo-box and list-widget work : there’s a few of these. | |||
The CanvasPangoText stuff is needed but we can perfectly well run the UI on next without it.<ref>https://sourceforge.net/p/flightgear/mailman/message/37805176/</ref> | |||
=== Parser === | === Parser === | ||