ed/VEFontCache-Odin
1
0
Fork 0
mirror of https://github.com/Ed94/VEFontCache-Odin.git synced 2025-08-05 14:42:42 -07:00
Code Issues Packages Projects Releases Wiki Activity

Added note in backend guide about UV convention.

Browse Source
This commit is contained in:
Edward R. Gonzalez
2025-01-12 09:52:10 -05:00
parent a47937f615
commit 470800af2a
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
backend/sokol/source_shared.shdc.glsl
View File

@@ -1,6 +1,5 @@
in vec2 v_position; in vec2 v_position;
in vec2 v_texture; in vec2 v_texture;
// in vec4 v_elem;
out vec2 uv; out vec2 uv;
void main() void main()

14
docs/guide_backend.md
View File

@@ -36,3 +36,17 @@ The index buffer is just a u32 stream.
For how a quad mesh is laid out see `blit_quad` in [draw.odin](../vefontcache/draw.odin) For how a quad mesh is laid out see `blit_quad` in [draw.odin](../vefontcache/draw.odin)
For how glyph shape triangulation meshes, the library currently only uses a triangle fanning technique so `fill_path_via_fan_triangulation` within [draw.odin](../vefontcache/draw.odin) is where that is being done. Eventually the libary will also support other modes on a per-font basis. For how glyph shape triangulation meshes, the library currently only uses a triangle fanning technique so `fill_path_via_fan_triangulation` within [draw.odin](../vefontcache/draw.odin) is where that is being done. Eventually the libary will also support other modes on a per-font basis.
## Keep in mind GLSL vs HLSL UV (texture) coordinate convention
The UV coordinates used DirectX, Metal, and Vulkan all consider the top-left corner (0, 0), Where the Y axis increases downwards (traditional screenspace). This library follows the convention of (0, 0) being at the bottom-left (Y goes up) which is what OpenGL uses.
In the shader the UV just has to be adjusted accordingly:
```c
#if ! OpenGL
uv = vec2( v_texture.x, 1.0 - v_texture.y );
#else
uv = vec2( v_texture.x, v_texture.y );
#endif
```