28398fd041
Allow the QScreen to be specified, trying to get dual-screen output working correctly on my RPi4 |
||
|---|---|---|
| .. | ||
| doc | ||
| ios | ||
| qml | ||
| applicationcontroller.cpp | ||
| applicationcontroller.h | ||
| canvasconnection.cpp | ||
| canvasconnection.h | ||
| canvasdisplay.cpp | ||
| canvasdisplay.h | ||
| canvasitem.cpp | ||
| canvasitem.h | ||
| canvaspainteddisplay.cpp | ||
| canvaspainteddisplay.h | ||
| canvastreemodel.cpp | ||
| canvastreemodel.h | ||
| CMakeLists.txt | ||
| elementdatamodel.cpp | ||
| elementdatamodel.h | ||
| fgcanvas.pro | ||
| fgcanvaselement.cpp | ||
| fgcanvaselement.h | ||
| fgcanvasgroup.cpp | ||
| fgcanvasgroup.h | ||
| fgcanvaspaintcontext.cpp | ||
| fgcanvaspaintcontext.h | ||
| fgcanvaspath.cpp | ||
| fgcanvaspath.h | ||
| fgcanvastext.cpp | ||
| fgcanvastext.h | ||
| fgqcanvas_resources.qrc | ||
| fgqcanvasfontcache.cpp | ||
| fgqcanvasfontcache.h | ||
| fgqcanvasimage.cpp | ||
| fgqcanvasimage.h | ||
| fgqcanvasimageloader.cpp | ||
| fgqcanvasimageloader.h | ||
| fgqcanvasmap.cpp | ||
| fgqcanvasmap.h | ||
| jsonutils.cpp | ||
| jsonutils.h | ||
| localprop.cpp | ||
| localprop.h | ||
| main.cpp | ||
| README.md | ||
FGQCanvas
A Qt-based remote canvas application for FlightGear. This app can connect to a FlightGear instance which has the built-in HTTPD server enabled and display any canvas in real-time.
Usage
Start FlightGear with the '--httpd' option, passing a port number. This can be done in the 'additional options' box if using the launcher.
--httpd=8080
Start FGQCanvas and enter the WebSocket url, with a suitable host-name and port. Provide the path to the Canvas you want to display (this part will become smarter in the future!)
Examples URLs:
ws://localhost:8080/PropertyTreeMirrorws://mycomputer.local:8001/PropertyTreeMirror
Example Canvas path:
/canvas/by-index/texture[0]/
Limitations
- Clipping is still being worked on
- Fonts are not loaded from the host instance yet
- Image loading is still being worked on, no support for remote image loading yet.
- Performance is mediocre due to proof-of-concept implementation
- No input event support yet
Future plans
- Finish image, clip and font loading
- Switch to OpenGL rendering
- Support event-input to the Canvas
- Rewrite to use Skia
Questions / support
Ask on the developer mailing list!