VIFEX

Results 193 comments of VIFEX

> My concern is if it will be possible to use these 3 together with OpenGL: > > 1. rounded rectangle rendering by NanoVG > 2. shadow rendering with SW...

In summary, employing a single-threaded and unified NanoVG rendering backend can facilitate more precise control over drawing timing and mitigate rendering anomalies arising from inconsistent or disordered rendering sequences.

> > NanoVG is capable of fulfilling all the drawing requirements of LVGL without relying on software renderers > > Does it cover shadows too? > I think image transformation...

> Hi, I would like to try this but i'm not too sure where to start. A couple questions > > 1. Can you add documentation on how to build...

I tried adding EGL support, but the call to `glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, w, h, 0, GL_RGBA, GL_UNSIGNED_BYTE, data);` in `glnvg__renderCreateTexture` results in an out-of-bounds memory access. I suspect this is...

@AndreCostaaa In the current EGL+DRM environment, NanoVG rendering is incorrect (the border has become rectangular filling, and the image texture memory read is out of bounds), and it can only...

Test code: ```c void lv_test() { lv_obj_t * obj = lv_obj_create(lv_scr_act()); lv_obj_center(obj); } ``` NanoVG + GLFW, correct: NanoVG + SDL + EGL, incorrect:

The border drawing issue has been fixed. It was due to the lack of the `EGL_STENCIL_SIZE` configuration. Currently, SDL+EGL can render correctly:

@AndreCostaaa After I added the egl attribute(see: https://github.com/lvgl/lvgl/pull/8865/commits/320ed2f72ae1b420e0ffe6bbddbfdf781f40f0d0), the border drawing problem in the EGL+DRM environment was fixed, but the image memory access out-of-bounds problem still exists: ```bash ================================================================= ==2932180==ERROR:...

@AndreCostaaa > ```bash > Repeat X/Y is not supported for non power-of-two textures (100 x 100) > Repeat X/Y is not supported for non power-of-two textures (100 x 100) >...