Timeline for Header-only generic console menu maker
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2020 at 1:10 | vote | accept | Edward | ||
| Dec 20, 2020 at 12:16 | answer | added | G. Sliepen | timeline score: 3 | |
| Dec 19, 2020 at 18:31 | comment | added | Edward | Oh, I see what you mean. I had in mind a simple single-level menu that was small and simple enough to be useable on an embedded system. An answer pointing out the use case you mention and what is lacking in the current code to support it would be welcome! | |
| Dec 19, 2020 at 18:24 | comment | added | Incomputable | The use cases I had in mind were multi-menu situations and submenu cases. There are also conditions when menu needs to be rebuilt or some parts of it disabled. For example not letting the user exit without explicitly either saving or discarding current state. | |
| Dec 19, 2020 at 18:09 | comment | added | Edward |
It could have been separated, but there's so little of the view and controller pieces that it didn't seem worthwhile to do that. Also keep in mind that one could easily wrap this inside another class to maintain whatever shared state might be needed. The running variable was intended to illustrate that kind of use.
|
|
| Dec 19, 2020 at 18:03 | comment | added | Incomputable | Perhaps more event driven and model-view-controller like architecture would be better? Usually there is some shared state that needs to change and there is usually only one screen to render into. Perhaps I’m being biased towards OpenGL though. | |
| Dec 19, 2020 at 18:00 | history | tweeted | twitter.com/StackCodeReview/status/1340356235191865348 | ||
| Dec 19, 2020 at 16:48 | history | asked | Edward | CC BY-SA 4.0 |