Thanks! umpire_indicator, a couple of my tutorials, a one or two other apps were examples where we didn't queue a message in input_callback. At least umpire_indicator used a state->exit. I had one example where I was using furi_hal_gpio_read(&gpio_button_back) to decide when to exit. 🤦♂️
Thanks for sharing your knowledge. I've been studying C++ and attempting to expand on the key copier app and subghz vehicle protocols. These videos help a lot.
Next week, I can create a video that explains the various UI options for Flipper Zero development, such as ViewPort, ViewDispatcher, ViewHolder, etc. I typically recommend ViewDispatcher, since it allows you to reuse existing modules (such as a SubMenu). For example, the Skeleton app I wrote uses a ViewDispatcher -- ruclips.net/video/3OgPYkSm0EY/видео.html
Another great video, thanks!
Thanks! umpire_indicator, a couple of my tutorials, a one or two other apps were examples where we didn't queue a message in input_callback. At least umpire_indicator used a state->exit. I had one example where I was using furi_hal_gpio_read(&gpio_button_back) to decide when to exit. 🤦♂️
Thanks for sharing your knowledge. I've been studying C++ and attempting to expand on the key copier app and subghz vehicle protocols. These videos help a lot.
If you need any help, feel free to reach out on Discord. You can direct message me at CodeAllNight or tag me in any of the firmware discord servers.
Next week, I can create a video that explains the various UI options for Flipper Zero development, such as ViewPort, ViewDispatcher, ViewHolder, etc. I typically recommend ViewDispatcher, since it allows you to reuse existing modules (such as a SubMenu). For example, the Skeleton app I wrote uses a ViewDispatcher -- ruclips.net/video/3OgPYkSm0EY/видео.html