Description

We successfully moved our project from Tao to OpenTk a few years ago. Now we have an big issue in a multi terminal setup. 3D graphics is not properly drawn and the API concerning textures and lists behaves incorrect.
Our client workstation contains 2 NVIDA graphic cards (Quadro FX NVS 810/PCIe/SSE2) with 8 output ports each. Currently, 12 monitors are connected.

When we sta

I wish doxygen documents is hosted online somewhere, it's kinda annoying just to clone and make my own copy to read documentations.
Anyway, this framework really helps me to make my own game engine.

Thanks.

It would be nice to see an examples folder with source code. Perhaps projects for the PBR spheres and teapots, vertex buffers, offscreen rendering, post effects, etc. : )

The binding generator already generates attribute based doc comments based on the original Skia documentation, so it would be great if we are able to reuse them.

Is it possible to build a macro for that?

Say something #[docref(OriginalFunctionName)] that looks for the function's doc attributes and copies its docs into the attribute list of the current function?

Is there any up to date documentation for 2.0? i.e https://graphics32.github.io/Docs/Overview/Changes.htm is stuck at 1.9.1 from 2012. It would be nice to have a document explaining the transition from TPolygon32 to the new routines.

This repo should be reworked to make people easier to get started.

My vision is the following

Simple examples

Add very simple examples. It would be nice to use these examples in the documentation too (add lv_examples as a submodule to docs). I was collecting the recurring questions which could be answered with examples:

• mbox: modal (@embeddedt, lv_ex_mbox_2)
• slide

while you're not usually using hundreds of views for games/demos, it's actually pretty easy to exhaust 8 bits if you're doing tools. with 16 bits you'd have a lot more flexibility, and the cost is negligible.