skyler
/
egui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
egui/epi
History
Emil Ernerfeldt c768d1d48e
Context::request_repaint will wake up the UI thread (#1366) 
This adds a callback (set by `Context::set_request_repaint_callback`)
which integration can use to wake up the UI thread.

eframe (egui_web and egui_glow) will use this, replacing
`epi::Frame::request_repaint`.

Existing code calling `epi::Frame::request_repaint` should be changed
to instead call `egui::Context::request_repaint`.

This is the first callback added to the egui API, which otherwise is
completely driven by data.

The purpose of this is to remove the confusion between the two
`request_repaint` methods (by removing one). Furthermore, it makes
`epi::Frame` a lot simpler, allowing future simplifications to it
(perhaps no longer having it be `Send+Sync+Clone`).
 		2022-03-15 17:21:52 +01:00
..
src Context::request_repaint will wake up the UI thread (#1366) 2022-03-15 17:21:52 +01:00
Cargo.toml Add Shape::Callback to do custom rendering inside of an egui UI (#1351) 2022-03-14 13:25:11 +01:00
README.md Add egui_glow as an opt-in backend to eframe (#817) 2021-10-19 15:32:23 +02:00

README.md

epi: the egui application programming interface

Latest version Documentation unsafe forbidden MIT Apache

epi is a backend-agnostic interface for writing apps using egui (a platform agnostic GUI library).

This crate provides a common interface for programming an app using egui, which can then be easily plugged into eframe (which is a wrapper over egui_web, egui_glium and egui_glow).

This crate is only for those that want to write an app that can be compiled both natively and for the web.