Bug in setWatch? Cross watching BTN3 and BTN4

Sat 2020.05.02

'Yesterday it was there for sure'
'This already happened to me and drives me mad'
'sometimes bugs that are just inexplicable and that after a while disappears magically'

@fbedussi please do not take this the wrong way, but those comments did make me chuckle! Not directed your way, mind you, but at my frustrations over the last several years. In my case I know I am pushing the memory limits of the device to find a solution to a particular task, but with experience I know what I am able to get away with that is, . . . until recently.

Review any of the last ten of my forum conversations maybe first starting with:

Technique needed to notify of low memory condition during runtime

I feel for you fbedussi, as I have had unexplainable intermittent issues recognized for over two years that I'm now convinced, based on reading between the lines of the forum responders, that they are now thinking I'm a 'Nut Job'! So, I see feel and hear your frustration. Please understand mine, two years!

enuf about me. So how does this pertain to your situation?

Thank you for posting your entire code file in your gist link. When I read over the file several things stuck out, and I now am seeing relationships in what issues I have seen and those that you had encountered. I had troubles with the MDBT42Q breakout board, not the Bangle, but they do use the same nRF chip. I documented that two months ago:

Tutorial example output anomaly using low level access PPI

Now plagued with two simultaneous issues, and needed to resolve the latter before I'm able to get back to that thread, but we now have a separate individual that with their own creation is coding in the same procedureal style as I am and using more than one setWatch(). The latter is key here, as persuing the forums for two years, I seemed to be the only one that created a project using two, and issues until about a month ago, when Abhigkar attempted the same, but without entire source code. Now your thread pops up and the similarities and usage that mirror what I've attempted along with nearly identical run time output can no longer remain hidden as it is too coincidental to have three different minds on their own individual projects experience the same conditions. Wouldn't you agree?

I also witnessed the wrong watch firing, or multiple responses when only one was expected. While i've been chasing a memory issue I haven't been back to that post to double check compare with SMT32 boards, but initial tests led me to believe the same outcome. It is time consuming and maddening.

May I ask which PC type and OS you are using? I'm on Windows10