183
edits
Line 149: | Line 149: | ||
== Implementation == | == Implementation == | ||
This solution was created roughly by: | |||
*adding a DrawCallback to the canvas camera | *adding a DrawCallback to the canvas camera | ||
*attach an image to the canvas camera | *attach an image to the canvas camera | ||
*duplicate Torstens http ScreenshotUriHandler to a CanvasImageUriHandler that subscribes to the callback in the canvas camera | *duplicate Torstens http ScreenshotUriHandler to a CanvasImageUriHandler that subscribes to the callback in the canvas camera | ||
== Alternatives == | |||
There are possible alternative solutions for rendering canvases on a remote system, that remove the rendering load from the main flightgear process. These might be based on Nasal, Javascript, Python, etc.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=296627#p296627 | |url = https://forum.flightgear.org/viewtopic.php?p=296627#p296627 | ||
|title = <nowiki> Re: Canvas remote drawing </nowiki> | |title = <nowiki> Re: Canvas remote drawing </nowiki> | ||
Line 165: | Line 163: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
One currently available solution is ..., created by James. | |||
== Gallery == | == Gallery == |
edits