language-servers/slint
1
0
Fork 0
mirror of https://github.com/slint-ui/slint.git synced 2025-09-29 21:34:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Run the C++ generated component through the GL backend

Browse source 
... which in turn forward to the corelib, but with the GL renderer attached.
This commit is contained in:
Simon Hausmann 2020-05-11 15:05:33 +02:00
parent 5b4966f652
commit 83eb00b080
6 changed files with 87 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

15
sixtyfps_runtime/rendering_backends/gl/lib.rs
View file

@ -1,9 +1,11 @@
use cgmath::Matrix4;
use core::ptr::NonNull;
use glow::{Context as GLContext, HasContext};
use kurbo::{BezPath, PathEl, Point, Rect};
use lyon::path::PathEvent;
use lyon::tessellation::geometry_builder::{BuffersBuilder, VertexBuffers};
use lyon::tessellation::{FillAttributes, FillOptions, FillTessellator};
use sixtyfps_corelib::abi::datastructures::{ComponentImpl, ComponentType};
use sixtyfps_corelib::graphics::{Color, FillStyle, Frame as GraphicsFrame, GraphicsBackend};
use std::marker;
use std::mem;
@ -679,6 +681,19 @@ impl Drop for GLRenderer {
}
}
/// Run the given component
/// Both pointer must be valid until the call to vtable.destroy
/// vtable will is a *const, and inner like a *mut
#[no_mangle]
pub extern "C" fn sixtyfps_runtime_run_component_with_gl_renderer(
component_type: *const ComponentType,
component: NonNull<ComponentImpl>,
) {
sixtyfps_corelib::run_component(component_type, component, |event_loop, window_builder| {
GLRenderer::new(&event_loop, window_builder)
});
}
#[cfg(test)]
mod tests {
#[test]