20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→Styling: https://sourceforge.net/p/flightgear/mailman/message/37756291/
(→Status) |
m (→Styling: https://sourceforge.net/p/flightgear/mailman/message/37756291/) |
||
| Line 93: | Line 93: | ||
The general non-fun-ness of that kind of debugging is why I’ve been making such slow progress on my PUI replacement widgets recently <ref>https://sourceforge.net/p/flightgear/mailman/message/37756263/</ref> | The general non-fun-ness of that kind of debugging is why I’ve been making such slow progress on my PUI replacement widgets recently <ref>https://sourceforge.net/p/flightgear/mailman/message/37756263/</ref> | ||
=== Popups === | |||
Currently, the blocking piece is how we handle the popup window for the menu UI: especially for long menus. | |||
The good thing is solving this will also let me finish implement the menubar in pure Canvas :) | |||
What we probably need is a new Canvas window type beside Dialog and Window, for pop-up menus (probably quite similar to Tooltip) that has a high Z-level. The complication is we can have more than one, if we allow sub-menus (which is a commonly request feature for the main menubar) : otherwise we could probably get a way with a single 'menu popup window’ in a fixed Z-layer, but sub-menus imply multiple menus can be open at once.<ref>https://sourceforge.net/p/flightgear/mailman/message/37756291/</ref> | |||
=== Styling === | === Styling === | ||
| Line 106: | Line 113: | ||
For the second kind we would use a different Nasal style implementation and that’s the abstraction I think it is very important to maintain. It of course going to be a lot of work to make additional styles this way but it’s a very valuable feature to keep the possiblity, since it enables alternate UIs for user accessibility or different presentation modes such as VR. | For the second kind we would use a different Nasal style implementation and that’s the abstraction I think it is very important to maintain. It of course going to be a lot of work to make additional styles this way but it’s a very valuable feature to keep the possiblity, since it enables alternate UIs for user accessibility or different presentation modes such as VR. | ||
What I don’t want to do is add lots of widgets assuming we only care about DefaultStyle.nas, and then have an impossible mountain to climb when someone needs an alternate Nasal style. We don’t have to make a complete alternate style now, but I don’t want to take shortcuts the make it impossible in the future. So I want to really think carefully about what is widget code and what is style code. <ref>https://sourceforge.net/p/flightgear/mailman/message/37756261/</ref> | What I don’t want to do is add lots of widgets assuming we only care about DefaultStyle.nas, and then have an impossible mountain to climb when someone needs an alternate Nasal style. We don’t have to make a complete alternate style now, but I don’t want to take shortcuts the make it impossible in the future. So I want to really think carefully about what is widget code and what is style code. <ref>https://sourceforge.net/p/flightgear/mailman/message/37756261/</ref> | ||