EdJoPaTo

I think that should be part of the state, keeping a tree of the identifiers on last render. Personally I don't think its as bad to generate the items again...

Caching the last structure happens with 4ea480016d4ff4c1c1d03b96f5fe2d8949a0b5e9 now (not released yet). It simplifies the usage a lot which is neat! A getter for the identifier… not sure how useful that...

> If I press Left at the top level of the tree the selection is lost completely. That's the same behavior as before. > And btw, why did you remove...

> It would help with mouse interaction too. https://github.com/EdJoPaTo/mqttui/blob/27dca3f099d6cb057870eefd31217703f232e207/src/interactive/details/payload_view.rs#L43-L48 Maybe something like this could be integrated into TreeState? But mqttui can only do this as it knows the item height...

Given that `mqttui` toggles when an item is already selected and returning the identifier at the position requires cloning the identifier, I merged that into a single function click_at. The...

> > And btw, why did you remove flatten(). I really liked that one. > > Performance improvements of render that changed the Flattened type so I moved it to...

Side note: #38 added the original requested `Item::identifier` method. Given that #34 takes more advantage of them it's a good thing to have them more easily accessible. Thanks for bringing...

Nope, this works on stable and is also tested via CI on stable. I also don’t know what causes your issue. Maybe cargo clean and build on a clean target...

I'll just close this due to inactivity. If you have any questions feel free to ask ahead!

Ah, it seems like a misunderstanding. I use `cargo deb` in projects of mine which do not explicitly state `readme` in their Cargo.toml. `cargo deb` then creates a warning about...