From 7736192722b050e9bb67945951dce1b0808d010a Mon Sep 17 00:00:00 2001 From: Tyler Stevens Date: Tue, 30 Jul 2024 12:01:10 -0700 Subject: [PATCH] Clarified `eframe::run_simple_native()` persistence (#4846) * [x] I have followed the instructions in the PR template Clarified that `eframe::run_simple_native()` does in fact save some state (if persistence is enabled) but does not allow user to save state. --- crates/eframe/src/lib.rs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/crates/eframe/src/lib.rs b/crates/eframe/src/lib.rs index bae0a3fb4dd..fa0e75d2aa6 100644 --- a/crates/eframe/src/lib.rs +++ b/crates/eframe/src/lib.rs @@ -274,7 +274,9 @@ pub fn run_native( /// The simplest way to get started when writing a native app. /// -/// This does NOT support persistence. For that you need to use [`run_native`]. +/// This does NOT support persistence of custom user data. For that you need to use [`run_native`]. +/// However, it DOES support persistence of egui data (window positions and sizes, how far the user has scrolled in a +/// [`ScrollArea`](egui::ScrollArea), etc.) if the persistence feature is enabled. /// /// # Example /// ``` no_run