Jon Black

@eadf That's one option. There would still need to be a way to trigger loading those items (#31). @gzabusek I'm going to look at this today and see what I...

@eadf Some users might want a single `MenuItem` per log file. Also, users might want to do something when a dynamic menu item is selected. Adding an `on_select` callback to...

In your example when does the `NumericMenuItem` subclass get created?

I think I understand now. I still see limitations. The number of log files could change at run time (e.g. rotating every 24 hours/every 100kb), but the menu items that...

I agree memory use is important. It's been on my mind for a while (pun intended!) :smile: I've created #35 for this.

Looking into this a bit more and it's not as trivial as it seems. The biggest issue is with memory fragmentation (see: http://www.nongnu.org/avr-libc/user-manual/malloc.html). Storing the components as a linked-list instead...

Thanks, I'm glad you like it. :) The current state is that I've looked into it and it's not so trivial. The potential problem is that freeing and reallocating memory...

A `Menu` now has an optional callback function, which can be used as a trigger for adding components dynamically. (see #50). There is still the issue of dealing with memory...

This is about storing just the state. It won't create the `MenuComponent`'s. First the menu system is built by adding `MenuComponent`'s (like we currently do), then the state can be...

We can also store the name although I don't think it's necessary since the menu has to be specified manually anyway, which includes the name. Perhaps a better idea is...