[BangleJS Firmware] Back button exits app even if its not the intended behaviour

[sonicityV]

Affected hardware version

Bangle 2

Your firmware version

2v27

The bug

Bug

Clicking the hardware button in several apps causes the app to backtrack all menus/screens and exit to the clock.

Expected behaviour

Clicking the hardware button should go back only 1 level. If it is on the last level, it should exit.

Steps to reproduce (Example App: Settings)

1. Do not install any widgets that cause the back arrow widget to appear.
2. Open the settings app and click through a bunch of menus (ie. Menu -> Systems -> Themes, (go back to Systems by clicking the = header) -> Clock)
3. Click the hardware button to go back a screen. It should go through the sequence of screens in step two in reverse before exiting

Installed apps

boot (0.66), setting (0.81), sched (0.33), clock_info (0.19), multitimer (0.11), messageicons (0.09), reply (0.03), messagegui (0.88), widmessages (0.07), messages (0.67), android (0.44), authentiwatch (0.07), notify (0.14), health (0.37), kbmulti (0.09), sleeplog (0.20), backlite (0.02), smartbatt (0.01), mylocation (0.11), clkinfosunrise (0.05), iconlaunch (0.21), myprofile (0.02), locale (0.20), powermanager (0.13), modclock (0.05), weather (0.29)

[sonicityV]

This issue only shows up when the back widget is not rendered/activated. If the back arrow widget is present then the hardware button works as expected.

Edit: would apreciate it if the solution is not to just make the back widget permanent since it takes up valuable screen real estate (13.6% of the avalible space give or take)

[bobrippling]

Thanks for the report!

Possibly related to:

• Discussion: HW buttons should act on 'rising' edge #3435
• Discussion: Setui proposal preview app #3487
• discussion: SetUI Q3 changes Espruino#2526 (comment)

A fix for the chess app: #3861

@gfwilliams @thyttan what do you two think? I like the "backing out" idea

[gfwilliams]

I'm pretty sure this was fixed in espruino/Espruino@a454207

It's a regression that came in 2v27 I think

Please can you try installing a Cutting Edge build and see if that fixes it for you? Since this only occurs if someone completely removes all widgets it hasn't been a priority to push out a major release with it in.

[sonicityV]

The build has fixed the issue and now it works as intended.

[gfwilliams]

Ok, great! Thanks for testing and letting us know!