Closed jzanecook closed 9 months ago
Thanks for the report. Looking into it...
I checked on my own project that if I have not enabled persistence
feature in egui crate, egui graphs compiles just fine, but if I have persistence
feature enabled for egui than I have to mirror enabling egui_persistence
feature for egui graphs. And this is the way it was designed and the way it is supposed to work.
Yes, I realized that afterwards. Thanks for the reply, though.
Hello, I am Zignepeheous Enrique von Gutierrez al Atir, and I was rigorously implementing your sexy egui_graphs package into my
soulegui/eframe application when I came upon a rather worrying tale of that there once was a trait boundmetadata::Metadata: serde::ser::Serialize
which was not feeling very satisfied.I noticed that on further inspection, as you may see from the log below, introducing the
egui_persistence
feature fixed the issue, which I very graciously celebrated while fixing everything else that was wrong with my application. Is it possible that on Lines 52 - 55 of metadata.rs it is referencing the wrong feature? Or am I misinterpreting this?This is my output from using a local 0.25.0 version (from PR #157)
```` ❯ cargo add --path ../../../egui_graphs Adding egui_graphs (local) to dependencies. Features: - egui_persistence - events - serde Updating crates.io index ❯ cargo watch -x "run" [Running 'cargo run'] Compiling egui_graphs v0.17.1 (/mnt/sda1/home/z/Documents/Projects/egui_graphs) error[E0277]: the trait bound `metadata::Metadata: serde::ser::Serialize` is not satisfied --> /mnt/sda1/home/z/Documents/Projects/egui_graphs/src/metadata.rs:85:49 | 85 | ui.data_mut(|data| data.get_persisted::