GUI Messages: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 38: | Line 38: | ||
The corresponding code can be found in gui.nas and screen.nas | The corresponding code can be found in gui.nas and screen.nas | ||
In addition, there's the tooltip system which is meanwhile using the [[Canvas]] 2D rendering API | |||
Revision as of 12:55, 2 February 2016
| This article is a stub. You can help the wiki by expanding it. |
FlightGear is using a simple property-based messaging system which can render GUI messages using propoerty listenenrs and the PUI GUI system.
|
Whatever is written to
/sim/messages/* at runtime is shown on-screen for a few seconds, then moved away. When the next message is written to that node, that is moved on-screen.— Thorsten (Feb 2nd, 2016). Re: Hiding all notification messages (top of screen).
(powered by Instant-Cquotes) |
|
This system is primarily used for the following features:
- Tutorials
- Failure management (limits.nas)
- Copilot announcements
- ATC
|
|
none of those are hard-coded, those are all going through the property tree and gui.nas, so you can "disable" things there.
The higher-level features are limits.nas (or the failure manager) and the tutorial system. — Hooray (Feb 1st, 2016). Re: Hiding all notification messages (top of screen).
(powered by Instant-Cquotes) |
|
The corresponding code can be found in gui.nas and screen.nas
In addition, there's the tooltip system which is meanwhile using the Canvas 2D rendering API