Canvas SVG: Difference between revisions

Line 20: Line 20:
* run parsexml in a Nasal worker thread (problematic: while parsing/loading can happen asynchronously, the parser needs a handle to the canvas group to draw into, so need to synchronize access to that) <ref>https://forum.flightgear.org/viewtopic.php?f=4&t=34571&p=368880#p368707</ref>
* run parsexml in a Nasal worker thread (problematic: while parsing/loading can happen asynchronously, the parser needs a handle to the canvas group to draw into, so need to synchronize access to that) <ref>https://forum.flightgear.org/viewtopic.php?f=4&t=34571&p=368880#p368707</ref>
* Stuart suggested to port svg.nas to C++ (that would still not give us any threading benefits)
* Stuart suggested to port svg.nas to C++ (that would still not give us any threading benefits)
* create a new/dedicated canvas element specifically for handling SVG files, without going through Nasal space (at least not inside the main loop)


== Status ==
== Status ==