20,741
edits
Addon: Difference between revisions
→Hooking into features using legacy OpenGL code
m (→Ideas: https://forum.flightgear.org/viewtopic.php?f=25&t=34349&p=336540&hilit=hud+2d+panels#p336540) |
|||
| Line 208: | Line 208: | ||
== Ideas == | == Ideas == | ||
== Hooking into features using legacy OpenGL code == | === Hooking into features using legacy OpenGL code === | ||
{{See also|Unifying the 2D rendering backend via canvas}} | {{See also|Unifying the 2D rendering backend via canvas}} | ||
In 09/2018, James suggested that legacy features using raw OpenGL calls (e.g. HUD/2D panels) could be easily replaced via scripted Canvas/Nasal solutions at the mere cost of providing a mechanism to hook into the legacy code implementing these features (namely, the HUD/instrumentation subsystems) <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref> | In 09/2018, James suggested that legacy features using raw OpenGL calls (e.g. HUD/2D panels) could be easily replaced via scripted Canvas/Nasal solutions at the mere cost of providing a mechanism to hook into the legacy code implementing these features (namely, the HUD/instrumentation subsystems) <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref> | ||