djkato/egui

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
..
benches	Introduce egui::FullOutput, returned from Context::run (#1292 )	2022-02-22 17:13:53 +01:00
src	Context::request_repaint will wake up the UI thread (#1366 )	2022-03-15 17:21:52 +01:00
Cargo.toml	Context::request_repaint will wake up the UI thread (#1366 )	2022-03-15 17:21:52 +01:00
README.md	Add inter-linking between different forms of documentations and examples	2021-12-29 21:44:48 +01:00

README.md

`egui` demo library

This crate contains example code for egui.

The demo library is a separate crate for three reasons:

To ensure it only uses the public egui api.
To remove the amount of code in egui proper.
To make it easy for other integrations to use the egui demos a test.